Triple
T11116064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Clemens, Michigan |
E262886
|
entity |
| Predicate | distanceToDetroitDowntown |
P25679
|
FINISHED |
| Object | approximately 20 miles |
—
|
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: approximately 20 miles | Statement: [Mount Clemens, Michigan, distanceToDetroitDowntown, approximately 20 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDetroitDowntown Context triple: [Mount Clemens, Michigan, distanceToDetroitDowntown, approximately 20 miles]
-
A.
distanceToDetroit
chosen
Indicates the measured or calculated spatial distance between a given entity and the location of Detroit.
-
B.
distanceToMadison
Indicates the spatial distance between a given entity and the location identified as Madison.
-
C.
distanceToMilwaukee
Indicates the measured or calculated spatial distance between a given entity’s location and the city of Milwaukee.
-
D.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
-
E.
distanceToMonroe
Indicates the measured distance between a given entity and the location named Monroe.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa81d8c81908a387b56cbcc9128 |
completed | April 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.