Triple
T37392377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brenda, Arizona |
E928751
|
entity |
| Predicate | locatedNearInterstate |
P75002
|
FINISHED |
| Object | Interstate 10 |
E81860
|
NE 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: Interstate 10 | Statement: [Brenda, Arizona, locatedNearInterstate, Interstate 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNearInterstate Context triple: [Brenda, Arizona, locatedNearInterstate, Interstate 10]
-
A.
nearInterstate
chosen
Indicates that one entity is located close to or in the immediate vicinity of an interstate highway.
-
B.
nearestInterstateHighway
Indicates that one interstate highway is the closest in distance to a given location or route compared to all other interstate highways.
-
C.
connectsToInterstate
Indicates that one roadway, route, or location has a direct connection or access point to an interstate highway.
-
D.
nearestInterstateExit
Indicates the relationship where a given location is associated with the closest interstate highway exit to it.
-
E.
interstateHighwayPassesThrough
Indicates that a specific interstate highway physically traverses or runs through the geographic area or jurisdiction of a given place.
- F. None of above.
Provenance (4 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40a7dd55b08190964b560246c3f9da |
completed | June 28, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.