Triple
T35597548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny: The Taken King |
E1028674
|
entity |
| Predicate | addsSubclass |
P183438
|
FINISHED |
| Object | Nightstalker |
—
|
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: Nightstalker | Statement: [Destiny: The Taken King, addsSubclass, Nightstalker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsSubclass Context triple: [Destiny: The Taken King, addsSubclass, Nightstalker]
-
A.
addsClass
Indicates that one entity introduces or appends a class (such as a classification, type, or code) to another entity.
-
B.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
-
C.
addsRegisterClass
Indicates that one entity assigns or associates a specific register class with another entity, typically extending or modifying its register-related behavior.
-
D.
hasMultipleSubclasses
Indicates that a class or category is related to more than one distinct subclass within a hierarchy.
-
E.
hasMutableSubclass
Indicates that a class has at least one subclass whose instances can be changed or modified after creation.
- 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.