Triple
T11542908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winston |
E273715
|
entity |
| Predicate | gameModeRole |
P68592
|
FINISHED |
| Object | Tank (role queue) |
—
|
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: Tank (role queue) | Statement: [Winston, gameModeRole, Tank (role queue)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameModeRole Context triple: [Winston, gameModeRole, Tank (role queue)]
-
A.
homeGameRole
Indicates that an entity participates in a game or match specifically in the role of the home side or host team.
-
B.
playRoleIn
chosen
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
C.
gammaRole
Indicates a tertiary or supporting role that an entity plays within a structured hierarchy of roles or participants in an event or relationship.
-
D.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
E.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e09eec8190894069d86b79183d |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.