Triple
T35010999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fallout engine |
E1009938
|
entity |
| Predicate | supportsCombatSystem |
P192587
|
FINISHED |
| Object | turn-based combat |
—
|
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: turn-based combat | Statement: [Fallout engine, supportsCombatSystem, turn-based combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCombatSystem Context triple: [Fallout engine, supportsCombatSystem, turn-based combat]
-
A.
compatibleWithCombatSystem
chosen
Indicates that one entity can function correctly and effectively within, or alongside, a specified combat system without conflicts or required modifications.
-
B.
usesCombatSystem
Indicates that one entity employs or operates a particular combat system in its functioning or behavior.
-
C.
hasCombat
Indicates that an entity engages in, is involved with, or possesses the capability for combat or fighting interactions with other entities.
-
D.
combatSystemFeature
Indicates that one entity is a feature, mechanic, or component belonging to or used within another entity’s combat system.
-
E.
hasCombatType
Indicates that an entity is associated with a particular mode or category of combat it uses or participates in.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.