Triple
T22789004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livingston (new town) |
E564054
|
entity |
| Predicate | hasArea |
P175
|
FINISHED |
| Object | Bankton |
—
|
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: Bankton | Statement: [Livingston (new town), hasArea, Bankton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bankton Context triple: [Livingston (new town), hasArea, Bankton]
-
A.
Bankton
chosen
Bankton is a residential area forming part of the town of Livingston in West Lothian, Scotland.
-
B.
Barrowton
Barrowton is a fortified town in the North of Westeros and the seat of House Dustin in the world of A Song of Ice and Fire.
-
C.
Boughton
Boughton is a small rural village in Norfolk, England, situated near the settlement of Stoke Ferry.
-
D.
Parkeston
Parkeston is a village and port area in Essex, England, situated near Harwich and known historically for its railway and maritime connections.
-
E.
Bradentown
Bradentown was the original name of the city now known as Bradenton, Florida, a Gulf Coast community in Manatee County.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c33be7c8190ad22391a85fa000d |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 3:29 p.m.