Triple
T30801869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Descent: Freespace – The Great War (Amiga port) |
E784389
|
entity |
| Predicate | hasCombatEnvironment |
P203528
|
FINISHED |
| Object | outer space |
—
|
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: outer space | Statement: [Descent: Freespace – The Great War (Amiga port), hasCombatEnvironment, outer space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCombatEnvironment Context triple: [Descent: Freespace – The Great War (Amiga port), hasCombatEnvironment, outer space]
-
A.
hasCombat
Indicates that an entity engages in, is involved with, or possesses the capability for combat or fighting interactions with other entities.
-
B.
hasCombatType
Indicates that an entity is associated with a particular mode or category of combat it uses or participates in.
-
C.
usesCombatSystem
Indicates that one entity employs or operates a particular combat system in its functioning or behavior.
-
D.
hasCombatRadius
Indicates the effective area or distance within which an entity can engage in or be involved in combat.
-
E.
hasPerspectiveOnCombat
Indicates a relationship where an entity holds a particular viewpoint, attitude, or stance regarding combat or warfare.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a019d1407588190b3b9b83fca2e61fe |
completed | May 11, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a019c760e3081909cfe9c0603727e48 |
completed | May 11, 2026, 9:08 a.m. |
| PDg | Predicate description generation | batch_6a019d12c1208190940abb0736c389b0 |
completed | May 11, 2026, 9:10 a.m. |
Created at: April 29, 2026, 8:42 p.m.