Triple
T33422665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battlefield series |
E855884
|
entity |
| Predicate | commonGameMode |
P46484
|
FINISHED |
| Object | Conquest |
—
|
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: Conquest | Statement: [Battlefield series, commonGameMode, Conquest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonGameMode Context triple: [Battlefield series, commonGameMode, Conquest]
-
A.
primaryGameMode
chosen
Indicates the main or default game mode associated with a particular game or gaming context.
-
B.
gameModeRelevance
Indicates how strongly or in what way something is related or applicable to a particular game mode.
-
C.
appearsInGameMode
Indicates that an entity is present, available, or featured within a specified game mode.
-
D.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
-
E.
gameModeRule
Indicates a rule or constraint that defines how a particular game mode operates or is played.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 1, 2026, 1:36 a.m.