Triple
T27402405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leavittsburg, Ohio |
E691887
|
entity |
| Predicate | distanceToWarrenInMiles |
P199808
|
FINISHED |
| Object | approximately 5 |
—
|
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 5 | Statement: [Leavittsburg, Ohio, distanceToWarrenInMiles, approximately 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToWarrenInMiles Context triple: [Leavittsburg, Ohio, distanceToWarrenInMiles, approximately 5]
-
A.
distanceFromWarren_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the location of Warren.
-
B.
distanceToWarwick
Indicates the spatial distance between a given entity and the location Warwick.
-
C.
distanceToWarburton
Indicates the spatial distance between a given entity and the location named Warburton.
-
D.
distanceToAnnArborApproxMiles
Indicates an approximate distance, measured in miles, between a given entity’s location and Ann Arbor.
-
E.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
| PDg | Predicate description generation | batch_69ff59b1e2ac8190bb65529e9dbbb178 |
completed | May 9, 2026, 3:58 p.m. |
Created at: April 27, 2026, 12:29 p.m.