Triple
T37011798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny 2: Shadowkeep |
E915969
|
entity |
| Predicate | addsDestination |
P186909
|
FINISHED |
| Object | Moon |
—
|
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: Moon | Statement: [Destiny 2: Shadowkeep, addsDestination, Moon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsDestination Context triple: [Destiny 2: Shadowkeep, addsDestination, Moon]
-
A.
sampleDestination
Indicates that something serves as, or is designated to be, the target location or endpoint for a sample.
-
B.
isDestinationFor
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
-
C.
usesDestination
Indicates that one entity directs or applies its action, movement, or output toward another entity as the intended destination.
-
D.
attemptedDestination
Indicates that an entity made an effort to reach or go to a particular destination, regardless of whether the attempt was successful.
-
E.
transferDestination
Indicates the entity that serves as the receiving end or target location of a transfer from another entity.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.