Triple
T2904242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mocksville, North Carolina |
E62724
|
entity |
| Predicate | distanceToWinstonSalem |
P42637
|
FINISHED |
| Object | approximately 25 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 25 miles southwest | Statement: [Mocksville, North Carolina, distanceToWinstonSalem, approximately 25 miles southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToWinstonSalem Context triple: [Mocksville, North Carolina, distanceToWinstonSalem, approximately 25 miles southwest]
-
A.
distanceToCharlotte
Indicates the measured or estimated distance between a given entity and the location Charlotte.
-
B.
distanceToGreensboroMiles
Indicates the physical distance, measured in miles, between a given location and Greensboro.
-
C.
distanceToPhiladelphia
Indicates the spatial distance between a given entity’s location and the city of Philadelphia.
-
D.
distanceToWashingtonDC
Indicates the physical distance between a given location and Washington, D.C.
-
E.
distanceToIndianapolis
Indicates the measured distance between a given entity’s location and the city of Indianapolis.
- 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_69ab4c3e070c8190b78d3d2c005876dd |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abe0cd68d48190aea4afbdaed2d4bc |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdd96670c8190b727f9ac27dadf67 |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:11 p.m.