Triple
T30801875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Descent: Freespace – The Great War (Amiga port) |
E784389
|
entity |
| Predicate | hasWeaponTypes |
P6014
|
FINISHED |
| Object | lasers |
—
|
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: lasers | Statement: [Descent: Freespace – The Great War (Amiga port), hasWeaponTypes, lasers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeaponTypes Context triple: [Descent: Freespace – The Great War (Amiga port), hasWeaponTypes, lasers]
-
A.
hasWeaponType
chosen
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
B.
hasWeaponOption
Indicates that an entity has a particular weapon available as a selectable or usable option.
-
C.
prohibitedWeaponType
Indicates that a particular type of weapon is classified as not allowed or forbidden under specified rules, laws, or agreements.
-
D.
weaponTypeTested
Indicates that a specific type of weapon has been subjected to a test or evaluation in the described context.
-
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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:42 p.m.