Triple
T34679787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battlefield V |
E890588
|
entity |
| Predicate | hasCampaignMode |
P200152
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Battlefield V, hasCampaignMode, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampaignMode Context triple: [Battlefield V, hasCampaignMode, yes]
-
A.
hasCampaignStructure
Indicates that one entity possesses, defines, or is associated with a particular organizational or strategic campaign framework of another entity.
-
B.
hasLiveMode
Indicates that an entity supports or is currently operating in a real-time, live-operation mode.
-
C.
hasChallengeMode
Indicates that an entity offers or is associated with a special, typically more difficult, challenge-oriented mode or setting.
-
D.
hasModeOfAction
Indicates that one entity (typically a treatment, drug, or intervention) exerts its effect through a specified mechanism or biological process.
-
E.
hasCampaignName
Indicates that an entity is associated with a specific campaign identified by a particular name.
- 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_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69ff779d3d788190af5a2dbc4d7ca3c8 |
completed | May 9, 2026, 6:06 p.m. |
Created at: May 1, 2026, 2:05 a.m.