Triple
T35433423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dequindre Road |
E1024129
|
entity |
| Predicate | passesThroughOrAlong |
P54144
|
FINISHED |
| Object | City of Detroit |
E2603
|
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: City of Detroit | Statement: [Dequindre Road, passesThroughOrAlong, City of Detroit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passesThroughOrAlong Context triple: [Dequindre Road, passesThroughOrAlong, City of Detroit]
-
A.
passedAlongside
Indicates that one entity moved or traveled next to another entity along the same route or path, maintaining a roughly parallel course.
-
B.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
C.
passesUnder
Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
-
D.
travelsThrough
chosen
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
-
E.
passesThroughFacility
Indicates that something (such as a person, object, or shipment) moves through or is routed via a particular facility as part of its path or process.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384a221e808190883e64979c627a22 |
completed | June 21, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.