Triple
T38530335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serious Sam 3: BFE |
E923345
|
entity |
| Predicate | includesEnemies |
P21502
|
FINISHED |
| Object | Beheaded Kamikaze |
E914322
|
NE 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: Beheaded Kamikaze | Statement: [Serious Sam 3: BFE, includesEnemies, Beheaded Kamikaze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEnemies Context triple: [Serious Sam 3: BFE, includesEnemies, Beheaded Kamikaze]
-
A.
combatantsIncluded
chosen
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
-
B.
hasEnemies
Indicates that one entity is in an antagonistic or hostile relationship with another, considering them an enemy.
-
C.
hasCommonEnemies
Indicates that two or more entities share at least one enemy in common.
-
D.
hasEnemiesTrait
Indicates that an entity possesses a characteristic or quality specifically related to having enemies.
-
E.
enemyCharacterIn
Indicates that a character is located within or present inside an enemy-controlled area, zone, or context.
- F. None of above.
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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41d670337081909450a3d14b334333 |
completed | June 29, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.