Triple
T8697693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | StarCraft II European ladder |
E206441
|
entity |
| Predicate | hasSeasonalStructure |
P84611
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [StarCraft II European ladder, hasSeasonalStructure, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonalStructure Context triple: [StarCraft II European ladder, hasSeasonalStructure, yes]
-
A.
hasSeasonalPattern
Indicates that the occurrence, intensity, or characteristics of something regularly vary according to a recurring seasonal cycle.
-
B.
hasSeasonalNature
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
-
C.
hasSeasonFrequency
Indicates how often something occurs or is scheduled within a specific season.
-
D.
hasSeasonalStatus
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
-
E.
hasSeasonalMigration
Indicates that an entity regularly moves between different locations according to seasonal or cyclical environmental changes.
- F. None of above. chosen
Provenance (4 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58af50408190a3b81100a759795e |
completed | March 31, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc582412f48190ae819965bfb0e75d |
completed | March 31, 2026, 11:26 p.m. |
Created at: March 30, 2026, 6:34 p.m.