Triple
T1710755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albany, Georgia |
E36976
|
entity |
| Predicate | distanceFromAtlantaApproxMiles |
P26813
|
FINISHED |
| Object | about 180 |
—
|
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: about 180 | Statement: [Albany, Georgia, distanceFromAtlantaApproxMiles, about 180]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAtlantaApproxMiles Context triple: [Albany, Georgia, distanceFromAtlantaApproxMiles, about 180]
-
A.
distanceToMontgomery
Indicates the spatial distance between a given entity and the location identified as Montgomery.
-
B.
distanceFromDallas
Indicates the measured distance between a given place or entity and the city of Dallas.
-
C.
approximateLengthInMiles
chosen
Indicates the estimated distance or extent of something measured in miles.
-
D.
distanceToCharlotte
Indicates the measured or estimated distance between a given entity and the location Charlotte.
-
E.
distanceToWashingtonDC
Indicates the physical distance between a given location and Washington, D.C.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab7521878c8190b9e7739b8c3fc705 |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61bd46d48190915500d75a9d8e94 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.