Triple
T15333169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diversey |
E366591
|
entity |
| Predicate | hasAdjacentStation |
P231
|
FINISHED |
| Object | Wellington |
E399981
|
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: Wellington | Statement: [Diversey, hasAdjacentStation, Wellington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wellington Context triple: [Diversey, hasAdjacentStation, Wellington]
-
A.
Wellington
chosen
Wellington is a Chicago Transit Authority 'L' station on the Brown Line located in the Lakeview neighborhood of Chicago, Illinois.
-
B.
Wellington
Wellington is a market town in Shropshire, England, now part of the borough of Telford and Wrekin.
-
C.
Wellington
Wellington is a small village in Lorain County, Ohio, known for its historic downtown and rural Midwestern character.
-
D.
Wellington
Wellington is a historic South African town in the Western Cape known for its wine, fruit farming, and scenic position at the foot of the Groenberg mountains.
-
E.
Wellington
Wellington is a masculine given name of English origin, historically associated with the title of the Duke of Wellington and later adopted as a personal name.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e0268608190947a58f559a67717 |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff01ecb904819082454622dcd77556 |
completed | May 9, 2026, 9:44 a.m. |
Created at: April 10, 2026, 3:17 a.m.