Triple
T28061478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kairakuen Park |
E709120
|
entity |
| Predicate | mainEventSeason |
P134483
|
FINISHED |
| Object | February |
—
|
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: February | Statement: [Kairakuen Park, mainEventSeason, February]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEventSeason Context triple: [Kairakuen Park, mainEventSeason, February]
-
A.
mainEventFor
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
-
B.
mainEventDate
Indicates the primary or most significant date on which the referenced event occurs or is scheduled to occur.
-
C.
mainEvents
Indicates that the referenced entities are the primary or most significant events within a given context, sequence, or narrative.
-
D.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
-
E.
seasonHighlightEvent
chosen
Indicates an event that stands out as a key or notable highlight 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 8:40 p.m.