Triple
T27319173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenison, Michigan |
E689438
|
entity |
| Predicate | distanceToGrandRapidsDowntown |
P199284
|
FINISHED |
| Object | approximately 10 miles southwest |
—
|
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 10 miles southwest | Statement: [Jenison, Michigan, distanceToGrandRapidsDowntown, approximately 10 miles southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGrandRapidsDowntown Context triple: [Jenison, Michigan, distanceToGrandRapidsDowntown, approximately 10 miles southwest]
-
A.
distanceToDetroit
Indicates the measured or calculated spatial distance between a given entity and the location of Detroit.
-
B.
directionFromGrandRapids
Indicates the cardinal or relative direction in which one entity is located from Grand Rapids.
-
C.
distanceToAnnArborApproxMiles
Indicates an approximate distance, measured in miles, between a given entity’s location and Ann Arbor.
-
D.
distanceToLansing
Indicates the spatial distance between a given entity’s location and the location of Lansing.
-
E.
distanceToMadison
Indicates the spatial distance between a given entity and the location identified as Madison.
- F. None of above. chosen
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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
| PDg | Predicate description generation | batch_69ff2d21f0a48190ad2ef5901cb07d93 |
completed | May 9, 2026, 12:48 p.m. |
Created at: April 27, 2026, 11:32 a.m.