Triple
T20098559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Hutt |
E496471
|
entity |
| Predicate | hasSuburb |
P747
|
FINISHED |
| Object | Wallaceville |
—
|
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: Wallaceville | Statement: [Upper Hutt, hasSuburb, Wallaceville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wallaceville Context triple: [Upper Hutt, hasSuburb, Wallaceville]
-
A.
Wallaceville
chosen
Wallaceville is a residential suburb located within the Hutt Valley region near Wellington, New Zealand.
-
B.
Mapleville
Mapleville is a small village and census-designated place located within the town of Burrillville in northern Rhode Island.
-
C.
Hattieville
Hattieville is a village in Belize known for housing the country’s main prison and serving as a residential community near Belize City.
-
D.
Almaville
Almaville is an unincorporated community located in Rutherford County, Tennessee, known for its rural residential character.
-
E.
Richville
Richville is a small unincorporated community located in Morgan County in the U.S. state of Missouri.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666e306c81909c0ef617e0f6fccf |
completed | April 20, 2026, 5:46 p.m. |
Created at: April 11, 2026, 11:25 p.m.