Triple
T11247734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny 2 (support studio) |
E266248
|
entity |
| Predicate | hasDeveloperRole |
P86457
|
FINISHED |
| Object | support development |
—
|
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: support development | Statement: [Destiny 2 (support studio), hasDeveloperRole, support development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeveloperRole Context triple: [Destiny 2 (support studio), hasDeveloperRole, support development]
-
A.
hasArchitectRole
Indicates that an entity holds or fulfills the role or function of an architect in relation to another entity or project.
-
B.
hasDevelopmentActor
chosen
Indicates that an entity is associated with or supported by a specific actor responsible for its development or advancement.
-
C.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
-
D.
hasProductionRole
Indicates that an entity holds a specific role or function in the production or creation process of another entity.
-
E.
hasSafetyRole
Indicates that an entity holds a responsibility or function related to safety within a given context or system.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e91d1484819098ee6b2efb5316a5 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.