Triple
T28030705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenida Entre Ríos |
E708256
|
entity |
| Predicate | hasRoadHierarchy |
P165312
|
FINISHED |
| Object | primary urban artery |
—
|
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: primary urban artery | Statement: [Avenida Entre Ríos, hasRoadHierarchy, primary urban artery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadHierarchy Context triple: [Avenida Entre Ríos, hasRoadHierarchy, primary urban artery]
-
A.
hasStreetHierarchyRole
Indicates that an entity holds a specific functional or positional role within a defined street hierarchy.
-
B.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
C.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
D.
hasRoadConfiguration
Indicates that there exists a specific arrangement or layout of roads associated with or characterizing an entity.
-
E.
hasRoadClass
chosen
Indicates that a road segment is assigned to a particular classification or category based on its type or functional importance.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 27, 2026, 8:16 p.m.