Triple
T27434172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin, West Virginia |
E690731
|
entity |
| Predicate | distanceToHarrisonburg, Virginia |
P199925
|
FINISHED |
| Object | approximately 40–50 miles west |
—
|
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 40–50 miles west | Statement: [Franklin, West Virginia, distanceToHarrisonburg, Virginia, approximately 40–50 miles west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToHarrisonburg, Virginia Context triple: [Franklin, West Virginia, distanceToHarrisonburg, Virginia, approximately 40–50 miles west]
-
A.
distanceToCharlottesville
Indicates the measured spatial distance between a given entity’s location and the location of Charlottesville.
-
B.
distanceToRichmond
Indicates the measured distance between a given location or entity and the place named Richmond.
-
C.
distanceFromFredericksburg
Indicates the measured distance between a given location and Fredericksburg.
-
D.
distanceToHarrisburg
Indicates the spatial distance between a given entity and the location of Harrisburg.
-
E.
distanceToNorfolkVirginia
Indicates the spatial distance between a given entity or location and Norfolk, Virginia.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
| PDg | Predicate description generation | batch_69ff64b864f481909fcefc2b08595c89 |
completed | May 9, 2026, 4:45 p.m. |
Created at: April 27, 2026, 12:43 p.m.