Triple
T7126585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lauderdale County |
E166076
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Killen, Alabama |
E689707
|
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: Killen, Alabama | Statement: [Lauderdale County, hasTown, Killen, Alabama]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Killen, Alabama Context triple: [Lauderdale County, hasTown, Killen, Alabama]
-
A.
Killen, Alabama
chosen
Killen, Alabama is a small town in northwestern Alabama known for its proximity to the Tennessee River and the Florence–Muscle Shoals metropolitan area.
-
B.
Eldridge, Alabama
Eldridge, Alabama is a small rural town located in Walker County in the northwestern part of the state.
-
C.
Steele, Alabama
Steele, Alabama is a small town in northeastern Alabama known for its rural character and location within St. Clair County.
-
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.
Billingsley, Alabama
Billingsley, Alabama is a small rural town in central Alabama known for its close-knit community and agricultural surroundings.
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e64ee8ac81909ee1c7cb1db3af33 |
completed | March 27, 2026, 8:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c9162980708190be2a347b2322c09c |
completed | March 29, 2026, 12:08 p.m. |
Created at: March 27, 2026, 2:44 p.m.