Triple
T7240195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walker County, Alabama |
E155333
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Oakman, Alabama |
E261278
|
NE 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: Oakman, Alabama | Statement: [Walker County, Alabama, hasTown, Oakman, Alabama]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oakman, Alabama Context triple: [Walker County, Alabama, hasTown, Oakman, Alabama]
-
A.
Oakman, Alabama
chosen
Oakman, Alabama is a small town in Walker County known for its historic roots in coal mining and its rural Southern community character.
-
B.
Shorterville, Alabama
Shorterville, Alabama is a small unincorporated community and rural locality in eastern Henry County near the Chattahoochee River.
-
C.
Eldridge, Alabama
Eldridge, Alabama is a small rural town located in Walker County in the northwestern part of the state.
-
D.
Sylvania, Alabama
Sylvania, Alabama is a small rural town in northeastern Alabama known for its close-knit community and location atop Sand Mountain.
-
E.
Jemison, Alabama
Jemison, Alabama is a small city in central Alabama known for its rural character and location along Interstate 65 between Birmingham and Montgomery.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea39230481908401ead83d8666cd |
completed | March 27, 2026, 8:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7cc3d75b48190916bf327396f2666 |
completed | March 28, 2026, 12:40 p.m. |
Created at: March 27, 2026, 2:55 p.m.