Triple
T14814801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madison, Georgia |
E348282
|
entity |
| Predicate | distanceToAthensGeorgia |
P101484
|
FINISHED |
| Object | about 30 miles south |
—
|
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 30 miles south | Statement: [Madison, Georgia, distanceToAthensGeorgia, about 30 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAthensGeorgia Context triple: [Madison, Georgia, distanceToAthensGeorgia, about 30 miles south]
-
A.
distanceToColumbusGeorgiaApprox
Indicates an approximate physical distance between a given location and Columbus, Georgia.
-
B.
distanceToAtlanta
Indicates the measured or calculated distance between a given location and the city of Atlanta.
-
C.
distanceToAthensCenter
chosen
Indicates the spatial distance between a given location and the center of Athens.
-
D.
distanceFromAthensAirport
Indicates the spatial distance between a given location and Athens Airport.
-
E.
distanceFromAthens_km
Indicates the physical distance, measured in kilometers, between a given place and the city of Athens.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe0e89c81908c0e1fe2bc3ebcfc |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:48 a.m.