Triple
T5654847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntersville |
E124591
|
entity |
| Predicate | distanceToCharlotteDowntown |
P28399
|
FINISHED |
| Object | approximately 12 miles north |
—
|
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 12 miles north | Statement: [Huntersville, distanceToCharlotteDowntown, approximately 12 miles north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCharlotteDowntown Context triple: [Huntersville, distanceToCharlotteDowntown, approximately 12 miles north]
-
A.
distanceToCharlotte
chosen
Indicates the measured or estimated distance between a given entity and the location Charlotte.
-
B.
distanceToWinstonSalem
Indicates the spatial distance between a given entity’s location and the city of Winston-Salem.
-
C.
distanceToAtlanta
Indicates the measured or calculated distance between a given location and the city of Atlanta.
-
D.
distanceFromDurhamCity
Indicates the measured distance between an entity’s location and the city of Durham.
-
E.
distanceToGreensboroMiles
Indicates the physical distance, measured in miles, between a given location and Greensboro.
- 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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022f998688190b18eb6469e8c054f |
completed | March 22, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69c01b2274b48190b2ef57ed728f785c |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:42 p.m.