Triple
T38645190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proleague |
E938695
|
entity |
| Predicate | transitionedGame |
P26626
|
FINISHED |
| Object | from StarCraft: Brood War to StarCraft II |
—
|
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: from StarCraft: Brood War to StarCraft II | Statement: [Proleague, transitionedGame, from StarCraft: Brood War to StarCraft II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionedGame Context triple: [Proleague, transitionedGame, from StarCraft: Brood War to StarCraft II]
-
A.
transitionState
Indicates a change in condition or phase from one defined state to another within a process or system.
-
B.
gamePlayed
Indicates that a particular game is or was played by an entity (such as a person, team, or group) during a specific event or time.
-
C.
transition
chosen
Indicates a change of state or condition from one form, phase, or situation to another.
-
D.
transitionedThrough
Indicates that an entity passed from one state, phase, or condition to another by way of an intermediate state, phase, or condition.
-
E.
turnedPro
Indicates that an individual transitioned from amateur status to professional status in a particular field or activity.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: May 3, 2026, 4:32 p.m.