Triple
T19610489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dilworth, Minnesota |
E470715
|
entity |
| Predicate | distanceToFargoDowntownInMiles |
P136460
|
FINISHED |
| Object | approximately 6 |
—
|
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 6 | Statement: [Dilworth, Minnesota, distanceToFargoDowntownInMiles, approximately 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToFargoDowntownInMiles Context triple: [Dilworth, Minnesota, distanceToFargoDowntownInMiles, approximately 6]
-
A.
distanceToWinnipeg
Indicates the spatial distance between a given entity’s location and the city of Winnipeg.
-
B.
distanceToSiouxFalls
Indicates the spatial distance between a given entity and the location of Sioux Falls.
-
C.
distanceToSaintPaul
Indicates the measured spatial distance between a given entity and the location of Saint Paul.
-
D.
distanceToMinneapolis
Indicates the measured distance between a given entity’s location and the city of Minneapolis.
-
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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640cb180c8190ba96ffb69c24e2e1 |
completed | April 20, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:43 p.m.