Triple
T37469846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overwatch World Cup 2019 |
E931125
|
entity |
| Predicate | featuredRoleLock |
P187135
|
FINISHED |
| Object | 2-2-2 role lock |
—
|
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: 2-2-2 role lock | Statement: [Overwatch World Cup 2019, featuredRoleLock, 2-2-2 role lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredRoleLock Context triple: [Overwatch World Cup 2019, featuredRoleLock, 2-2-2 role lock]
-
A.
hadRoleLock
chosen
Indicates that an entity’s role was restricted or fixed, preventing changes to that role during a certain period or context.
-
B.
secretRole
Indicates that an entity holds a role or function that is intentionally hidden or not publicly disclosed within a given context.
-
C.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
D.
specialRole
Indicates that an entity holds a distinctive or exceptional function, status, or responsibility in relation to another entity or context.
-
E.
usesRoleTypes
Indicates that an entity employs or is associated with specific role classifications or role types within a given context.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.