Triple
T28562888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emerado, North Dakota |
E722594
|
entity |
| Predicate | distanceToGrandForksNorthDakotaMiles |
P201789
|
FINISHED |
| Object | approximately 16 |
—
|
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 16 | Statement: [Emerado, North Dakota, distanceToGrandForksNorthDakotaMiles, approximately 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGrandForksNorthDakotaMiles Context triple: [Emerado, North Dakota, distanceToGrandForksNorthDakotaMiles, approximately 16]
-
A.
distanceToGrandForksAirForceBaseMiles
Indicates the physical distance, measured in miles, between a given location and Grand Forks Air Force Base.
-
B.
distanceToFargoDowntownInMiles
Indicates the number of miles between a given location and downtown Fargo.
-
C.
distanceToSiouxFalls
Indicates the spatial distance between a given entity and the location of Sioux Falls.
-
D.
distanceToWinnipeg
Indicates the spatial distance between a given entity’s location and the city of Winnipeg.
-
E.
distanceToFortWorth_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a002249ee388190a9501ee7630dc658 |
completed | May 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a002189273881909b6b687e2d61f5b1 |
completed | May 10, 2026, 6:11 a.m. |
| PDg | Predicate description generation | batch_6a0022494be881908bdf945d2393a40f |
completed | May 10, 2026, 6:14 a.m. |
Created at: April 28, 2026, 4:05 a.m.