Triple
T4167180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South West |
E84473
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bunbury |
E51812
|
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: Bunbury | Statement: [South West, contains, Bunbury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bunbury Context triple: [South West, contains, Bunbury]
-
A.
Bunbury
chosen
Bunbury is a coastal city in Western Australia known as a regional port and commercial hub south of Perth.
-
B.
Hotton
Hotton is a small Belgian town in the Ardennes region, known for its scenic riverside setting, caves, and outdoor recreation along the Ourthe River.
-
C.
Farnum
Farnum is a locality within Providence County, Rhode Island, likely a small village or neighborhood rather than an incorporated city.
-
D.
Marple
Marple is a suburban town in the Metropolitan Borough of Stockport, Greater Manchester, England, known for its canals, locks, and proximity to the Peak District.
-
E.
Fosby
Fosby is a settlement that serves as the main local hub and seat of administration for the surrounding Aremark area in Norway.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02c43a7481909eed7cb8c14deb0c |
completed | March 9, 2026, 5:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b57f4a022c819092b5489aa47f430c |
completed | March 14, 2026, 3:31 p.m. |
Created at: March 9, 2026, 3:44 p.m.