Triple
T11540844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soap MacTavish |
E273668
|
entity |
| Predicate | roleInCallOfDuty4ModernWarfare |
P99595
|
FINISHED |
| Object | playable protagonist |
—
|
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: playable protagonist | Statement: [Soap MacTavish, roleInCallOfDuty4ModernWarfare, playable protagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCallOfDuty4ModernWarfare Context triple: [Soap MacTavish, roleInCallOfDuty4ModernWarfare, playable protagonist]
-
A.
roleDuringBlackHawkWar
Indicates the specific role, position, or function an entity held during the Black Hawk War.
-
B.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
C.
favoredMilitaryRole
Indicates the military position, function, or specialization that an entity prefers or is most inclined to choose.
-
D.
roleInCombatSystem
Indicates the specific function or responsibility an entity has within a combat or battle mechanics framework.
-
E.
roleInAH64
Indicates that an entity has a specific functional role or position in relation to the AH-64 attack helicopter.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886deed5c81908e5c38156064f882 |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d8279925e4819089210611c0d8e61a |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 8, 2026, 9:37 p.m.