Triple
T7914023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashville, Alabama |
E183771
|
entity |
| Predicate | isOneOfCountySeatsOf |
P27090
|
FINISHED |
| Object | St. Clair County, Alabama |
—
|
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: St. Clair County, Alabama | Statement: [Ashville, Alabama, isOneOfCountySeatsOf, St. Clair County, Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOneOfCountySeatsOf Context triple: [Ashville, Alabama, isOneOfCountySeatsOf, St. Clair County, Alabama]
-
A.
isInCountySeatOf
Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
-
B.
hasCountySeatOf
chosen
Indicates that a place serves as the administrative county seat (capital) of a specified county.
-
C.
hasCountySeatRelation
Indicates that a specific place serves as the county seat (administrative center) of a particular county.
-
D.
hasCountySeatWithRole
Indicates that a county has a designated county seat that fulfills a specific administrative or governmental role.
-
E.
isInCountySeat
Indicates that one entity (typically a place or facility) is located within the county seat of a given county.
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a748f4c8190bcd868de2fcf0b3a |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:04 p.m.