Triple
T35597559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny: The Taken King |
E1028674
|
entity |
| Predicate | addsActivity |
P108310
|
FINISHED |
| Object | Court of Oryx |
—
|
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: Court of Oryx | Statement: [Destiny: The Taken King, addsActivity, Court of Oryx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsActivity Context triple: [Destiny: The Taken King, addsActivity, Court of Oryx]
-
A.
addsGroupActivity
chosen
Indicates that an entity performs an action to include or associate a group activity with another entity.
-
B.
exportActivity
Indicates an action where goods, services, or data are sent out from one entity or region to another for trade or distribution across borders.
-
C.
activity
Indicates that an entity is engaged in or performing a particular action, behavior, or process.
-
D.
associatedActivity
Indicates that one entity is linked to, involved in, or characterized by a particular activity or set of activities.
-
E.
supportsActivity
Indicates that one entity provides the necessary conditions, resources, or environment for another entity’s activity to occur or be sustained.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.