Triple
T8881093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSMC Wellington |
E211411
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Wellington |
E18156
|
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: [RSMC Wellington, locatedIn, Wellington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wellington Context triple: [RSMC Wellington, locatedIn, Wellington]
-
A.
Wellington
Wellington is a regional town in New South Wales, Australia, known for its agricultural surroundings and location near the junction of the Macquarie and Bell rivers.
-
B.
Wellington
Wellington is a Chicago Transit Authority 'L' station on the Brown Line located in the Lakeview neighborhood of Chicago, Illinois.
-
C.
Wellington
chosen
Wellington is the compact, hilly coastal city at the southern tip of New Zealand’s North Island known for its vibrant arts scene, windy climate, and role as the country’s political and cultural hub.
-
D.
Wellington
Wellington is a market town in Shropshire, England, now part of the borough of Telford and Wrekin.
-
E.
Wellington
Wellington is a small village in Lorain County, Ohio, known for its historic downtown and rural Midwestern character.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6168e3d881908c58cf11cf5f9a0e |
completed | April 1, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfabc1992481909e8a4216086d5111 |
completed | April 3, 2026, noon |
Created at: March 30, 2026, 6:52 p.m.