Triple
T34679803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battlefield V |
E890588
|
entity |
| Predicate | singlePlayerStoriesSetting |
P179610
|
FINISHED |
| Object | various World War II fronts |
—
|
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: various World War II fronts | Statement: [Battlefield V, singlePlayerStoriesSetting, various World War II fronts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singlePlayerStoriesSetting Context triple: [Battlefield V, singlePlayerStoriesSetting, various World War II fronts]
-
A.
hasSinglePlayer
Indicates that something includes, supports, or is designed for a single-player mode or experience.
-
B.
isSideStoryTo
Indicates that one narrative work is a supplementary or tangential story that expands on, but is not central to, the main storyline of another work.
-
C.
hasStandaloneGame
Indicates that an entity has its own independently released, self-contained game associated with it.
-
D.
hasModernDayStoryline
Indicates that the work’s narrative is set in, or primarily takes place during, contemporary or present-day times.
-
E.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72327346881909caa001dc0107b23 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 2:05 a.m.