Triple
T28562887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emerado, North Dakota |
E722594
|
entity |
| Predicate | distanceToGrandForksAirForceBaseMiles |
P201776
|
FINISHED |
| Object | approximately 2 |
—
|
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 2 | Statement: [Emerado, North Dakota, distanceToGrandForksAirForceBaseMiles, approximately 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGrandForksAirForceBaseMiles Context triple: [Emerado, North Dakota, distanceToGrandForksAirForceBaseMiles, approximately 2]
-
A.
distanceToFargoDowntownInMiles
Indicates the number of miles between a given location and downtown Fargo.
-
B.
distanceFromFairbanks
Indicates the spatial distance between a given location or entity and the city of Fairbanks.
-
C.
distanceToSiouxFalls
Indicates the spatial distance between a given entity and the location of Sioux Falls.
-
D.
distanceToFortWorth
Indicates the spatial distance between a given location and the city of Fort Worth.
-
E.
distanceToMinneapolis
Indicates the measured distance between a given entity’s location and the city of Minneapolis.
- 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_6a002103c93081908398fa5726f5fa6e |
completed | May 10, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_6a001fcb9fb48190a27d8f2ca983fbe6 |
completed | May 10, 2026, 6:03 a.m. |
| PDg | Predicate description generation | batch_6a00210313c08190ab581c505ef46b8e |
completed | May 10, 2026, 6:09 a.m. |
Created at: April 28, 2026, 4:05 a.m.