Triple
T15459199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appomattox Station |
E371851
|
entity |
| Predicate | distanceToAppomattoxCourtHouse |
P118309
|
FINISHED |
| Object | approximately 3 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 3 miles | Statement: [Appomattox Station, distanceToAppomattoxCourtHouse, approximately 3 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAppomattoxCourtHouse Context triple: [Appomattox Station, distanceToAppomattoxCourtHouse, approximately 3 miles]
-
A.
distanceFromJamestown
Indicates the measured distance between a given location and Jamestown.
-
B.
distanceToRichmond
Indicates the measured distance between a given location or entity and the place named Richmond.
-
C.
distanceToHarrisburg
Indicates the spatial distance between a given entity and the location of Harrisburg.
-
D.
distanceToMontpelierApprox
Indicates an approximate measure of how far one entity is from Montpelier, typically expressed as a distance value.
-
E.
distanceToAnnapolisMiles
Indicates the physical distance, measured in miles, between a given location and Annapolis.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f1623f0819086f6fc2bfd536609 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:32 a.m.