Triple
T38173082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coração de Maria |
E1000131
|
entity |
| Predicate | telephoneSystemContext |
P97956
|
FINISHED |
| Object | Brazilian telephone numbering plan |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Brazilian telephone numbering plan | Statement: [Coração de Maria, telephoneSystemContext, Brazilian telephone numbering plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telephoneSystemContext Context triple: [Coração de Maria, telephoneSystemContext, Brazilian telephone numbering plan]
-
A.
telecommunicationSystem
Indicates a relationship where communication between entities is carried out over a distance using electronic or digital transmission systems.
-
B.
callNumberSystem
Indicates a relationship where an entity uses or is organized according to a particular call number system for classification or identification.
-
C.
telephoneSystemCountry
Indicates that a telephone system operates within, or is associated with, a specific country.
-
D.
telephoneStandard
Indicates that there is a relationship involving the use of a particular telephone standard or protocol for communication between entities.
-
E.
telephoneNumberingScope
chosen
Indicates the range or domain within which a particular telephone number or numbering plan is valid, managed, or applicable.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:29 p.m.