Triple
T28687029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oakley, Kansas |
E729161
|
entity |
| Predicate | distanceToMonumentRocks |
P201913
|
FINISHED |
| Object | approximately 25 miles south |
—
|
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 25 miles south | Statement: [Oakley, Kansas, distanceToMonumentRocks, approximately 25 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMonumentRocks Context triple: [Oakley, Kansas, distanceToMonumentRocks, approximately 25 miles south]
-
A.
distanceToMonumentValley
Indicates the spatial distance between a given entity and Monument Valley.
-
B.
distanceToFourCornersMonumentInMiles
Indicates the numerical distance, measured in miles, between an entity’s location and the Four Corners Monument.
-
C.
distanceToWashingtonMonument
Indicates the physical distance between a given entity’s location and the Washington Monument.
-
D.
distanceToMountRushmore
Indicates the measured or calculated spatial distance between an entity and Mount Rushmore.
-
E.
distanceToUluru
Indicates the spatial distance between a given entity and Uluru.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a0031ed5d708190ab93516ad081ada6 |
completed | May 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_6a0031b5dbd081908eb0f4dbb8a0eac3 |
completed | May 10, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_6a0031ec758c81908a3877bc19ce2701 |
completed | May 10, 2026, 7:21 a.m. |
Created at: April 28, 2026, 5:33 a.m.