Triple
T8697686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | StarCraft II European ladder |
E206441
|
entity |
| Predicate | includesPlayerType |
P6384
|
FINISHED |
| Object | professional players |
—
|
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: professional players | Statement: [StarCraft II European ladder, includesPlayerType, professional players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPlayerType Context triple: [StarCraft II European ladder, includesPlayerType, professional players]
-
A.
participantType
chosen
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
B.
includesGameType
Indicates that one entity contains or supports a particular type or category of game.
-
C.
supportsParticipantType
Indicates that an entity is compatible with, or designed to work with, a specified type or category of participant.
-
D.
supportsPlayers
Indicates that an entity provides compatibility or functionality for one or more players to participate or be used.
-
E.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
- 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_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. |
Created at: March 30, 2026, 6:34 p.m.