Triple
T37040823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny 2: Beyond Light |
E916775
|
entity |
| Predicate | introducesSubclass |
P183438
|
FINISHED |
| Object | Stasis |
—
|
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: Stasis | Statement: [Destiny 2: Beyond Light, introducesSubclass, Stasis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesSubclass Context triple: [Destiny 2: Beyond Light, introducesSubclass, Stasis]
-
A.
addsSubclass
chosen
Indicates that one entity is being declared or introduced as a subclass of another, establishing an inheritance or specialization relationship between them.
-
B.
usesSubclass
Indicates that one entity makes use of, depends on, or operates through a more specific subclass of another entity.
-
C.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
-
D.
classIntroduced
Indicates that a particular class (e.g., in a programming language or system) has been newly defined or made available within a given context or scope.
-
E.
introducedAsPartOfClass
Indicates that something was introduced as a component or element within a particular class or course.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 3, 2026, 4:14 p.m.