Triple
T5283694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fultondale High School |
E119559
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Fultondale |
E22170
|
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: Fultondale | Statement: [Fultondale High School, city, Fultondale]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fultondale Context triple: [Fultondale High School, city, Fultondale]
-
A.
Fultondale, Alabama
chosen
Fultondale, Alabama is a small suburban city in Jefferson County that serves as a northern gateway community to the Birmingham metropolitan area.
-
B.
Ferndale
Ferndale is a former coal-mining town and community located in the Rhondda Fach valley in south Wales.
-
C.
Ferndale
Ferndale is a small city in northwestern Washington State, known for its proximity to the Canadian border and the city of Bellingham.
-
D.
Gardendale, Alabama
Gardendale, Alabama is a suburban city in Jefferson County that serves as a residential community just north of Birmingham.
-
E.
Meridianville, Alabama
Meridianville, Alabama is a suburban community in Madison County, just north of Huntsville, known for its residential neighborhoods and proximity to the growing Huntsville metropolitan area.
- 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_69bd446d05a8819092ad333a3f9c8d5c |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd84c8d2bc8190840699e5a526b756 |
completed | March 20, 2026, 5:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf06e6200881908da623e8548ec051 |
completed | March 21, 2026, 9 p.m. |
Created at: March 20, 2026, 1:52 p.m.