Triple
T38507255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crookston, Minnesota |
E921797
|
entity |
| Predicate | distanceToGrandForksND |
P201789
|
FINISHED |
| Object | about 25 miles east |
—
|
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: about 25 miles east | Statement: [Crookston, Minnesota, distanceToGrandForksND, about 25 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGrandForksND Context triple: [Crookston, Minnesota, distanceToGrandForksND, about 25 miles east]
-
A.
distanceToGrandForksNorthDakotaMiles
chosen
Indicates the physical distance, measured in miles, between an entity and Grand Forks, North Dakota.
-
B.
distanceToGrandForksAirForceBaseMiles
Indicates the physical distance, measured in miles, between a given location and Grand Forks Air Force Base.
-
C.
distanceToFargoDowntownInMiles
Indicates the number of miles between a given location and downtown Fargo.
-
D.
distanceTo Fargo, North Dakota
Indicates the measured spatial distance between a given location and Fargo, North Dakota.
-
E.
distanceToWinnipeg
Indicates the spatial distance between a given entity’s location and the city of Winnipeg.
- 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.