Triple
T36951826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny 2: Forsaken |
E914084
|
entity |
| Predicate | raidLairOrActivity |
P100069
|
FINISHED |
| Object | Scourge of the Past |
—
|
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: Scourge of the Past | Statement: [Destiny 2: Forsaken, raidLairOrActivity, Scourge of the Past]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidLairOrActivity Context triple: [Destiny 2: Forsaken, raidLairOrActivity, Scourge of the Past]
-
A.
associatedRaid
chosen
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
B.
notableGameLocation
Indicates that a particular place is recognized as a significant or prominent location within a game.
-
C.
notableSanctuaryLocation
Indicates that a location is recognized as a significant or distinguished sanctuary site for the associated entity.
-
D.
majorDungeonFeature
Indicates that something serves as a primary or defining structural or thematic element of a dungeon.
-
E.
hasLair
Indicates that an entity maintains or occupies a specific place as its lair or den.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.