Triple
T29341741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soldier of Fortune |
E744053
|
entity |
| Predicate | numberOfSinglePlayerMissions |
P201322
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Soldier of Fortune, numberOfSinglePlayerMissions, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSinglePlayerMissions Context triple: [Soldier of Fortune, numberOfSinglePlayerMissions, 10]
-
A.
numberOfMissions
Indicates the total count of missions associated with a given entity or context.
-
B.
numberOfSuccessfulMissions
Indicates the count of missions that have been completed successfully by the referenced entity or within the specified context.
-
C.
hasMissionSystem
Indicates that an entity is equipped with or associated with a specific mission-related system or subsystem.
-
D.
containsMission
Indicates that one entity includes or encompasses a mission as part of its contents, scope, or responsibilities.
-
E.
appearsInMission
Indicates that an entity participates in, is featured in, or occurs within a particular mission.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69ffebbcef80819099714fa9b7fda762 |
completed | May 10, 2026, 2:21 a.m. |
Created at: April 28, 2026, 1:34 p.m.