Triple
T38645143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBCGame Starleague |
E938694
|
entity |
| Predicate | competitionGame |
P17867
|
FINISHED |
| Object | StarCraft: Brood War |
—
|
NE NERFINISHED |
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: StarCraft: Brood War | Statement: [MBCGame Starleague, competitionGame, StarCraft: Brood War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionGame Context triple: [MBCGame Starleague, competitionGame, StarCraft: Brood War]
-
A.
competitiveGame
Indicates a relationship where entities participate in a game or contest in which they compete against each other to win or achieve a higher ranking.
-
B.
competitionPlayed
Indicates that a competitive event or match has taken place between participants.
-
C.
competition
Indicates a relationship where two or more entities strive against each other to achieve a superior outcome, advantage, or reward.
-
D.
competitionInception
Indicates the point in time or event at which a competition is first established or begins to exist.
-
E.
competitionOf
chosen
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
- 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_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 3, 2026, 4:32 p.m.