Triple
T31817678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casselton, North Dakota |
E812179
|
entity |
| Predicate | distanceTo Fargo, North Dakota |
P203857
|
FINISHED |
| Object | approximately 20 miles west |
—
|
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 20 miles west | Statement: [Casselton, North Dakota, distanceTo Fargo, North Dakota, approximately 20 miles west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceTo Fargo, North Dakota Context triple: [Casselton, North Dakota, distanceTo Fargo, North Dakota, approximately 20 miles west]
-
A.
distanceToFargoDowntownInMiles
Indicates the number of miles between a given location and downtown Fargo.
-
B.
distanceToGrandForksNorthDakotaMiles
Indicates the physical distance, measured in miles, between an entity and Grand Forks, North Dakota.
-
C.
distanceToWinnipeg
Indicates the spatial distance between a given entity’s location and the city of Winnipeg.
-
D.
distanceToGrandForksAirForceBaseMiles
Indicates the physical distance, measured in miles, between a given location and Grand Forks Air Force Base.
-
E.
distanceToFortWorth
Indicates the spatial distance between a given location and the city of Fort Worth.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0226c8b2f881909de3c1a5ba40fc49 |
completed | May 11, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_6a0225602acc8190978ab4aacc615b8d |
completed | May 11, 2026, 6:52 p.m. |
| PDg | Predicate description generation | batch_6a0226c7f31c819093c2049efccbacbc |
completed | May 11, 2026, 6:58 p.m. |
Created at: April 30, 2026, 11:45 p.m.