Triple
T30871568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irmo, South Carolina |
E786355
|
entity |
| Predicate | distanceToColumbiaDowntown |
P1299
|
FINISHED |
| Object | approximately 10 miles northwest |
—
|
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 northwest | Statement: [Irmo, South Carolina, distanceToColumbiaDowntown, approximately 10 miles northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToColumbiaDowntown Context triple: [Irmo, South Carolina, distanceToColumbiaDowntown, approximately 10 miles northwest]
-
A.
distanceToColumbiaMissouri
Indicates the measured or calculated distance between a given entity’s location and Columbia, Missouri.
-
B.
directionFromColumbia
Indicates the cardinal or relative direction in which one entity is located from Columbia.
-
C.
distanceFromDowntown
chosen
Indicates the physical distance between a given location and the central downtown area.
-
D.
distanceToColumbus
Indicates the spatial distance between a given entity and the location of Columbus.
-
E.
distanceFromMedellín
Indicates the measured spatial distance between an entity and the city of Medellín.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a016cc5abcc8190b64094c777b40f6f |
completed | May 11, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_6a016b997ecc8190818207c57b9cbf17 |
completed | May 11, 2026, 5:39 a.m. |
Created at: April 29, 2026, 8:48 p.m.