Triple
T18849714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sete Rios |
E461007
|
entity |
| Predicate | hasNearbyRoad |
P11435
|
FINISHED |
| Object |
Eixo Norte-Sul
Eixo Norte-Sul is a major urban expressway in Lisbon, Portugal, connecting the city’s northern and southern zones and serving as a key traffic artery.
|
E1346018
|
NE FINISHED |
How this triple was built (4 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: Eixo Norte-Sul | Statement: [Sete Rios, hasNearbyRoad, Eixo Norte-Sul]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eixo Norte-Sul Context triple: [Sete Rios, hasNearbyRoad, Eixo Norte-Sul]
-
A.
Eje 1 Norte
Eje 1 Norte is a major east–west arterial road in Mexico City that forms part of the city’s primary ring and grid traffic system.
-
B.
Eje 2 Norte
Eje 2 Norte is a major east–west arterial road in Mexico City that forms part of the city’s structured “eje vial” traffic network.
-
C.
Eje 1 Sur
Eje 1 Sur is a major east–west arterial road in Mexico City that forms part of the city’s structured “eje vial” traffic network.
-
D.
Eje Central
Eje Central is a Mexico City Metro station on Line 12 located along the major north–south thoroughfare Eje Central Lázaro Cárdenas.
-
E.
Land Axis
Land Axis is a major ceremonial and visual alignment in Canberra’s Parliamentary Triangle that connects key national landmarks and structures.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Eixo Norte-Sul Triple: [Sete Rios, hasNearbyRoad, Eixo Norte-Sul]
Generated description
Eixo Norte-Sul is a major urban expressway in Lisbon, Portugal, connecting the city’s northern and southern zones and serving as a key traffic artery.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Eixo Norte-Sul Target entity description: Eixo Norte-Sul is a major urban expressway in Lisbon, Portugal, connecting the city’s northern and southern zones and serving as a key traffic artery.
-
A.
Eje 1 Norte
Eje 1 Norte is a major east–west arterial road in Mexico City that forms part of the city’s primary ring and grid traffic system.
-
B.
Eje 2 Norte
Eje 2 Norte is a major east–west arterial road in Mexico City that forms part of the city’s structured “eje vial” traffic network.
-
C.
Eje 1 Sur
Eje 1 Sur is a major east–west arterial road in Mexico City that forms part of the city’s structured “eje vial” traffic network.
-
D.
Eje Central
Eje Central is a Mexico City Metro station on Line 12 located along the major north–south thoroughfare Eje Central Lázaro Cárdenas.
-
E.
Land Axis
Land Axis is a major ceremonial and visual alignment in Canberra’s Parliamentary Triangle that connects key national landmarks and structures.
- F. None of above. chosen
Provenance (5 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8f1abdc819081638ed384da191e |
completed | April 20, 2026, 5:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0567778ef08190af337b59cb345eed |
completed | May 14, 2026, 6:11 a.m. |
| NEDg | Description generation | batch_6a056c57c32481908b14f6a830a0e3e9 |
completed | May 14, 2026, 6:31 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a056cf897188190b46a7c662c639d88 |
completed | May 14, 2026, 6:34 a.m. |
Created at: April 10, 2026, 11:56 a.m.