Triple
T21514536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nihon Shirīzu |
E530808
|
entity |
| Predicate | hasSeasonPhase |
P75603
|
FINISHED |
| Object | championship series |
—
|
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: championship series | Statement: [Nihon Shirīzu, hasSeasonPhase, championship series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonPhase Context triple: [Nihon Shirīzu, hasSeasonPhase, championship series]
-
A.
seasonPhaseCovered
Indicates that a particular phase or segment of a season is included or encompassed within a specified scope, period, or coverage.
-
B.
hasPhaseOfPlay
chosen
Indicates a relationship where a broader game or activity includes or is associated with a specific phase or segment of play.
-
C.
hasRegularSeason
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
-
D.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
-
E.
hasSeasonalStatus
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea89b6e48190ac4ea139b895714f |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.