Triple
T37096296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny 2: The Witch Queen |
E918572
|
entity |
| Predicate | introducesWeaponType |
P35807
|
FINISHED |
| Object | Glaive |
—
|
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: Glaive | Statement: [Destiny 2: The Witch Queen, introducesWeaponType, Glaive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesWeaponType Context triple: [Destiny 2: The Witch Queen, introducesWeaponType, Glaive]
-
A.
introducedWeaponSystem
chosen
Indicates that an entity caused a new weapon system to be brought into use or formally adopted.
-
B.
hasWeaponType
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
C.
involvesWeaponType
Indicates that the relationship or action includes the use, presence, or association of a specific type or category of weapon.
-
D.
typicalWeapon
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
E.
weaponTypeTested
Indicates that a specific type of weapon has been subjected to a test or evaluation in the described context.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: May 3, 2026, 4:14 p.m.