Triple
T36951834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny 2: Forsaken |
E914084
|
entity |
| Predicate | hasSubclassUpdate |
P4061
|
FINISHED |
| Object | new super for each subclass |
—
|
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: new super for each subclass | Statement: [Destiny 2: Forsaken, hasSubclassUpdate, new super for each subclass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubclassUpdate Context triple: [Destiny 2: Forsaken, hasSubclassUpdate, new super for each subclass]
-
A.
hasMutableSubclass
Indicates that a class has at least one subclass whose instances can be changed or modified after creation.
-
B.
usesSubclass
Indicates that one entity makes use of, depends on, or operates through a more specific subclass of another entity.
-
C.
hasMultipleSubclasses
Indicates that a class or category is related to more than one distinct subclass within a hierarchy.
-
D.
isUpdatedThrough
Indicates that one entity’s state or content is modified or brought up to date as a result of a process, action, or interaction involving another entity.
-
E.
isUpdated
chosen
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or a reference point.
- 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_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4:13 p.m.