Triple
T22479023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ericsson Stadium |
E555711
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Auckland |
—
|
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: Auckland | Statement: [Ericsson Stadium, location, Auckland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Auckland Context triple: [Ericsson Stadium, location, Auckland]
-
A.
Auckland
chosen
Auckland is a major New Zealand metropolis known for its harbors, multicultural population, and role as the country’s primary economic and transport hub.
-
B.
Wellington
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.
-
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 small community located in Prince County on Prince Edward Island, Canada.
-
E.
Wellington
Wellington is a small community on Prince Edward Island, Canada, known for its rural character and access to the island’s recreational trail network.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be653bc8190a2e5c47e38228bfe |
completed | April 29, 2026, 1:16 a.m. |
Created at: April 16, 2026, 8:49 p.m.