Triple
T37835287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Vengeful Heart of Ender |
E943321
|
entity |
| Predicate | appearsInDLC |
P39175
|
FINISHED |
| Object | Echoing Void |
—
|
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: Echoing Void | Statement: [The Vengeful Heart of Ender, appearsInDLC, Echoing Void]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInDLC Context triple: [The Vengeful Heart of Ender, appearsInDLC, Echoing Void]
-
A.
hasDLC
chosen
Indicates that one entity includes, is associated with, or is supplemented by another entity as downloadable content.
-
B.
DLCName
Indicates that the associated value is the name or title of a specific downloadable content (DLC) package related to the entity.
-
C.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
D.
appearsOnDeluxeEdition
Indicates that an item (such as a track or feature) is included specifically on the deluxe edition of a work rather than (or in addition to) the standard edition.
-
E.
DLCNumber
Indicates the identifier or count assigned to a specific downloadable content (DLC) item associated with something.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 3, 2026, 4:19 p.m.