Triple
T34679812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battlefield V |
E890588
|
entity |
| Predicate | supportsCrossPlatformPlay |
P40488
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Battlefield V, supportsCrossPlatformPlay, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCrossPlatformPlay Context triple: [Battlefield V, supportsCrossPlatformPlay, no]
-
A.
supportsCrossPlay
chosen
Indicates that one platform, system, or service allows users on different platforms to interact or play together across those platforms.
-
B.
supportsOnlineMultiplayer
Indicates that the subject provides functionality for multiple users to play together over an online network.
-
C.
supportsLocalMultiplayer
Indicates that the subject provides functionality for multiple players to play together on the same device or local network.
-
D.
multiplayerCompatibleWith
Indicates that two or more entities can function together in a shared multiplayer context without conflict or incompatibility.
-
E.
transferableBetweenConsoles
Indicates that something (such as data, content, or progress) can be moved or shared from one gaming console to another.
- 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_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:05 a.m.