Triple
T7708760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuquay-Varina, North Carolina |
E174692
|
entity |
| Predicate | distanceFromRaleigh |
P76683
|
FINISHED |
| Object | approximately 18 miles southwest |
—
|
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 18 miles southwest | Statement: [Fuquay-Varina, North Carolina, distanceFromRaleigh, approximately 18 miles southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromRaleigh Context triple: [Fuquay-Varina, North Carolina, distanceFromRaleigh, approximately 18 miles southwest]
-
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.
directionFromRaleigh
Indicates the cardinal or relative compass direction in which one location lies when measured from Raleigh.
-
D.
distanceToCharlotte
Indicates the measured or estimated distance between a given entity and the location Charlotte.
-
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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:04 p.m.