Triple
T19279070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calle-Calle Bridge |
E482136
|
entity |
| Predicate | isMajorCrossingInCity |
P37486
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Calle-Calle Bridge, isMajorCrossingInCity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorCrossingInCity Context triple: [Calle-Calle Bridge, isMajorCrossingInCity, true]
-
A.
hasMajorCrossing
Indicates that one entity has a significant or primary intersection or crossing with another entity.
-
B.
hasMajorRailCrossing
Indicates that there is a significant railway crossing (such as a major rail line intersecting a road or another transport route) at or associated with the referenced location or entity.
-
C.
isMajorRoadJunction
chosen
Indicates that a location serves as a primary intersection where major roads or highways meet or cross.
-
D.
isMajorInterchangeFor
Indicates that one location functions as a primary hub where multiple routes or lines connect or transfer between each other for another location.
-
E.
isLocalCrossroads
Indicates that a location serves as a junction where multiple local routes or streets intersect.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbf817c819098745ed365cda4a9 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.