Triple
T20190956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inklings |
E492975
|
entity |
| Predicate | notableGameModeParticipation |
P69305
|
FINISHED |
| Object | Turf War |
—
|
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: Turf War | Statement: [Inklings, notableGameModeParticipation, Turf War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGameModeParticipation Context triple: [Inklings, notableGameModeParticipation, Turf War]
-
A.
notableGameRound
Indicates that a particular game round is especially significant or noteworthy within the context of the game or competition.
-
B.
performedInGame
Indicates that an action or event was carried out during a particular game or match.
-
C.
notableGameEvent
Indicates that a specific game is associated with a significant or noteworthy event in its history or context.
-
D.
appearsInGameMode
chosen
Indicates that an entity is present, available, or featured within a specified game mode.
-
E.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad593f88190a1e534fed38b3cd7 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.