Triple
T29341765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soldier of Fortune |
E744053
|
entity |
| Predicate | supportsLANPlay |
P40438
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Soldier of Fortune, supportsLANPlay, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLANPlay Context triple: [Soldier of Fortune, supportsLANPlay, true]
-
A.
supportsLocalMultiplayer
chosen
Indicates that the subject provides functionality for multiple players to play together on the same device or local network.
-
B.
hasMultiplayer
Indicates that an entity (such as a game or application) supports a mode where multiple users can participate or interact simultaneously.
-
C.
supportsOnlineMultiplayer
Indicates that the subject provides functionality for multiple users to play together over an online network.
-
D.
hasMultiplayerCoop
Indicates that an entity (such as a game or application) supports a multiplayer mode where multiple users can cooperate or play together simultaneously.
-
E.
multiplayerCompatibleWith
Indicates that two or more entities can function together in a shared multiplayer context without conflict or incompatibility.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a03213d35788190bdf04e19625b4060 |
completed | May 12, 2026, 12:46 p.m. |
| PD | Predicate disambiguation | batch_6a031ea131d48190ab0fecb48b8e2205 |
completed | May 12, 2026, 12:35 p.m. |
Created at: April 28, 2026, 1:34 p.m.