Triple
T11223478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Clair Shores |
E265631
|
entity |
| Predicate | distanceToDetroitDowntownMiles |
P25679
|
FINISHED |
| Object | approximately 13 |
—
|
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 13 | Statement: [St. Clair Shores, distanceToDetroitDowntownMiles, approximately 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDetroitDowntownMiles Context triple: [St. Clair Shores, distanceToDetroitDowntownMiles, approximately 13]
-
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.
distanceToMarquetteInMiles
Indicates the numerical distance, measured in miles, between a given entity’s location and Marquette.
-
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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ec8fb08190b27144ab65f85957 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.