Triple
T29273297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgantown |
E742176
|
entity |
| Predicate | distanceToCharlestonWV |
P202342
|
FINISHED |
| Object | approximately 160 miles |
—
|
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 160 miles | Statement: [Morgantown, distanceToCharlestonWV, approximately 160 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCharlestonWV Context triple: [Morgantown, distanceToCharlestonWV, approximately 160 miles]
-
A.
distanceToCharlestonMi
Indicates the measured distance, in miles, from a given entity or location to Charleston.
-
B.
distanceToCharlottesville
Indicates the measured spatial distance between a given entity’s location and the location of Charlottesville.
-
C.
distanceToMorgantownMi
Indicates the measured distance from a given entity or location to Morgantown, Michigan.
-
D.
distanceToCharlotte
Indicates the measured or estimated distance between a given entity and the location Charlotte.
-
E.
distanceToRichmond
Indicates the measured distance between a given location or entity and the place named Richmond.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a0075be7f54819081ab12bc1dab53bb |
completed | May 10, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a0073a19030819098c23faa3adcb96e |
completed | May 10, 2026, 12:01 p.m. |
| PDg | Predicate description generation | batch_6a0075bd35e08190b604777ae9fbbe4b |
completed | May 10, 2026, 12:10 p.m. |
Created at: April 28, 2026, 12:49 p.m.