Triple
T24629894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand Kiwis |
E609642
|
entity |
| Predicate | homeTestVenue |
P150009
|
FINISHED |
| Object | Mount Smart Stadium |
—
|
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: Mount Smart Stadium | Statement: [New Zealand Kiwis, homeTestVenue, Mount Smart Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTestVenue Context triple: [New Zealand Kiwis, homeTestVenue, Mount Smart Stadium]
-
A.
home venue type
Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
-
B.
homeVenueName
chosen
Indicates the name of the primary venue or location where an entity (such as a team, event, or organization) regularly hosts its home activities.
-
C.
homeMeetsVenue
Indicates that a home team plays its scheduled match at a specified venue.
-
D.
hostsVenue
Indicates that an entity provides or manages a location where an event or activity takes place.
-
E.
firstTestVenue
Indicates the venue where something (such as an event, performance, or test) was held or conducted for the first time.
- F. None of above.
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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.