Triple
T25545888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedmont, Alabama |
E640300
|
entity |
| Predicate | isTrailTownFor |
P158862
|
FINISHED |
| Object | Chief Ladiga Trail |
—
|
NE NERFINISHED |
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: Chief Ladiga Trail | Statement: [Piedmont, Alabama, isTrailTownFor, Chief Ladiga Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTrailTownFor Context triple: [Piedmont, Alabama, isTrailTownFor, Chief Ladiga Trail]
-
A.
isTown
Indicates that the subject entity is classified as a town.
-
B.
isInteriorTownOf
Indicates that one town is located within the interior region of, and is administratively or geographically associated with, a larger area or jurisdiction.
-
C.
isScenicTown
Indicates that a town is visually attractive or picturesque, often due to its natural surroundings, architecture, or overall aesthetic appeal.
-
D.
isResortTown
Indicates that a town functions primarily as a resort destination, typically focused on tourism, leisure, and vacation activities.
-
E.
isRailTrail
Indicates that a path or route is a rail trail, meaning it follows or repurposes a former or existing railway corridor for recreational or transportation use.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f897fa5081909a0ff39571e22d98 |
completed | May 2, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 3:29 p.m.