Triple
T37685892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reckoning |
E938364
|
entity |
| Predicate | includesExoZombiesChapter |
P6720
|
FINISHED |
| Object | Descent |
E932030
|
NE 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: Descent | Statement: [Reckoning, includesExoZombiesChapter, Descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesExoZombiesChapter Context triple: [Reckoning, includesExoZombiesChapter, Descent]
-
A.
containsChapter
chosen
Indicates that one entity (typically a larger work or document) includes another entity as a chapter within its structure.
-
B.
appearsInAppendicesOf
Indicates that one entity is included or referenced within the appendices section of another entity.
-
C.
hasLocalChaptersIn
Indicates that an organization maintains one or more local chapters or branches within a specified geographic area or location.
-
D.
containsSubchapter
Indicates that one chapter or section includes another, more specific subchapter as a part of its structure.
-
E.
hasGeneralChapter
Indicates that an entity is associated with, or contains, a general chapter (a broad or overarching section) within a larger structured document or framework.
- F. None of above.
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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40cdba8f8081909cc6df3e20d80360 |
completed | June 28, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.