Triple
T9322966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emporia, Virginia |
E224314
|
entity |
| Predicate | distanceToRaleighInMiles |
P76683
|
FINISHED |
| Object | approximately 80 |
—
|
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 80 | Statement: [Emporia, Virginia, distanceToRaleighInMiles, approximately 80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToRaleighInMiles Context triple: [Emporia, Virginia, distanceToRaleighInMiles, approximately 80]
-
A.
distanceToRaleighApproxMiles
chosen
Indicates the approximate distance, measured in miles, between a given place and Raleigh.
-
B.
distanceToWinstonSalem
Indicates the spatial distance between a given entity’s location and the city of Winston-Salem.
-
C.
distanceToCharlotte
Indicates the measured or estimated distance between a given entity and the location Charlotte.
-
D.
distanceToGreensboroMiles
Indicates the physical distance, measured in miles, between a given location and Greensboro.
-
E.
distanceFromDurhamCity
Indicates the measured distance between an entity’s location and the city of Durham.
- F. None of above.
Provenance (3 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_69ca8426d48481909596360f7791c7dd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd36f466b08190884abdc56501a0d8 |
completed | April 1, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:38 p.m.