Triple
T34679806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battlefield V |
E890588
|
entity |
| Predicate | hasBattlePassLikeSystem |
P103266
|
FINISHED |
| Object | Tides of War |
—
|
NE NERFINISHED |
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: Tides of War | Statement: [Battlefield V, hasBattlePassLikeSystem, Tides of War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattlePassLikeSystem Context triple: [Battlefield V, hasBattlePassLikeSystem, Tides of War]
-
A.
hasBattlePassIntegration
chosen
Indicates that an entity is functionally connected to or supports features of a battle pass system.
-
B.
hasBadgeSystem
Indicates that an entity includes or supports a badge-based system for recognizing or tracking achievements, statuses, or milestones.
-
C.
belongsToSeasonPass
Indicates that an item, access right, or feature is included as part of a specific season pass.
-
D.
hasBattleFormat
Indicates that an entity is associated with, or conducted under, a particular battle or combat ruleset or format.
-
E.
hasProgressionSystem
Indicates that an entity includes or is associated with a structured system through which progress, advancement, or development can occur over time.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 2:05 a.m.