Triple
T26766821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ark Encounter |
E674960
|
entity |
| Predicate | distanceFromCincinnati |
P197974
|
FINISHED |
| Object | approximately 40 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 40 miles south | Statement: [Ark Encounter, distanceFromCincinnati, approximately 40 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromCincinnati Context triple: [Ark Encounter, distanceFromCincinnati, approximately 40 miles south]
-
A.
distanceToColumbus
Indicates the spatial distance between a given entity and the location of Columbus.
-
B.
distanceToCleveland
Indicates the measured distance between a given entity or location and the city of Cleveland.
-
C.
distanceToIndianapolis
Indicates the measured distance between a given entity’s location and the city of Indianapolis.
-
D.
distanceToDayton
Indicates the spatial distance between a given entity or location and the city of Dayton.
-
E.
distanceFromUrbana
Indicates the measured spatial distance between a given entity or location and Urbana.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
| PDg | Predicate description generation | batch_69fec00e5c1c819083d174bb4bc35f29 |
completed | May 9, 2026, 5:03 a.m. |
Created at: April 27, 2026, 4 a.m.