Triple
T35418571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunedin Stadium |
E1023715
|
entity |
| Predicate | hasSecondaryUseSeason |
P150429
|
FINISHED |
| Object | summer |
—
|
LITERAL 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: summer | Statement: [Dunedin Stadium, hasSecondaryUseSeason, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryUseSeason Context triple: [Dunedin Stadium, hasSecondaryUseSeason, summer]
-
A.
hasUseSeason
chosen
Indicates the season or time of year during which something is intended or suitable to be used.
-
B.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
-
C.
usedSeasonallyBy
Indicates that something is utilized or employed by an entity only during specific seasons or times of the year.
-
D.
usedForSeasonRange
Indicates the span of seasons or time period during which something is intended or suitable to be used.
-
E.
usedInSeason
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: May 3, 2026, 4:03 p.m.