Triple
T27528545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eixão |
E694904
|
entity |
| Predicate | isMajorTransportArteryFor |
P18708
|
FINISHED |
| Object | Brasília |
—
|
NE NERFINISHED |
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: Brasília | Statement: [Eixão, isMajorTransportArteryFor, Brasília]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorTransportArteryFor Context triple: [Eixão, isMajorTransportArteryFor, Brasília]
-
A.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
B.
isMajorTrafficRoute
Indicates that a road or pathway serves as a primary, heavily used route for traffic flow within a transportation network.
-
C.
hasMajorTransportationRole
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
-
D.
isMajorArterialFor
chosen
Indicates that something functions as a primary high-capacity route or conduit serving as a main channel for movement, flow, or traffic for something else.
-
E.
isMajorTransportLink
Indicates that something serves as a primary or highly significant route or connection for transporting people or goods between places.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 1:25 p.m.