Triple
T34679793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battlefield V |
E890588
|
entity |
| Predicate | FirestormModeType |
P179609
|
FINISHED |
| Object | battle royale |
—
|
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: battle royale | Statement: [Battlefield V, FirestormModeType, battle royale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FirestormModeType Context triple: [Battlefield V, FirestormModeType, battle royale]
-
A.
fireModes
Indicates the different ways or settings in which a weapon or device can be fired or operated.
-
B.
fireType
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
-
C.
burnMode
Indicates that one entity is operating in or causing a state of intense, high-output, or destructive activity in another entity or process.
-
D.
underFire
Indicates that an entity is being attacked, heavily criticized, or subjected to intense pressure by another entity or group.
-
E.
fireUse
Indicates the use or application of fire by one entity on, with, or for another entity or object.
- 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.