Triple
T35597545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny: The Taken King |
E1028674
|
entity |
| Predicate | addsRaid |
P183436
|
FINISHED |
| Object | King's Fall |
—
|
NE NERFINISHED |
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: King's Fall | Statement: [Destiny: The Taken King, addsRaid, King's Fall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsRaid Context triple: [Destiny: The Taken King, addsRaid, King's Fall]
-
A.
associatedRaid
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
B.
addsPublicDungeon
Indicates that an entity introduces or includes a public dungeon as part of its content or structure.
-
C.
hasRaid
Indicates that an entity is associated with, participates in, or is the target of a raid event or operation.
-
D.
addsQuest
Indicates that one entity assigns or introduces a quest to another entity or into a system.
-
E.
majorRaid
Indicates a large-scale, coordinated attack or incursion carried out against a target.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:05 p.m.