Triple
T18711822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarboro, North Carolina |
E457531
|
entity |
| Predicate | distanceToRockyMountMiles |
P132385
|
FINISHED |
| Object | 17 |
—
|
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: 17 | Statement: [Tarboro, North Carolina, distanceToRockyMountMiles, 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToRockyMountMiles Context triple: [Tarboro, North Carolina, distanceToRockyMountMiles, 17]
-
A.
distanceToGreatSmokyMountainsNationalPark
Indicates the spatial distance between an entity and Great Smoky Mountains National Park.
-
B.
distanceToWhiteMountainPeak
Indicates the measured or calculated distance between a given entity and the peak of White Mountain.
-
C.
distanceToMountRushmore
Indicates the measured or calculated spatial distance between an entity and Mount Rushmore.
-
D.
distanceToRaleighApproxMiles
Indicates the approximate distance, measured in miles, between a given place and Raleigh.
-
E.
distanceToMountRainierNationalParkEntranceInMiles
Indicates the numerical distance, measured in miles, from a given location to the entrance of Mount Rainier National Park.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5671c53988190bfc132c853cebd02 |
completed | April 19, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e478e0889c8190a118d67b200ce8ef |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:50 a.m.