Triple

T33217285
Position Surface form Disambiguated ID Type / Status
Subject Angerthas Erebor E850320 entity
Predicate usedInAppendix P196510 FINISHED
Object Appendix E of The Lord of the Rings 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: Appendix E of The Lord of the Rings | Statement: [Angerthas Erebor, usedInAppendix, Appendix E of The Lord of the Rings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedInAppendix
Context triple: [Angerthas Erebor, usedInAppendix, Appendix E of The Lord of the Rings]
  • A. areUsedIn
    Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
  • B. usedInLibrary
    Indicates that something is utilized or applied within the context of a library, such as a software library or a physical library system.
  • C. usedInPartOf
    Indicates that something is utilized or plays a functional role within a specific component or subpart of a larger whole.
  • D. alsoUsedIn
    Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
  • E. usedInStructure
    Indicates that something (such as a material, component, or element) is employed as part of the composition or construction of a larger structure.
  • 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_69f3496083dc8190b229bb6932dc548b completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fe59d11e9881909d2f33b7c717030e completed May 8, 2026, 9:46 p.m.
PD Predicate disambiguation batch_69fe394fdfbc8190a931926ae3635cbf completed May 8, 2026, 7:28 p.m.
PDg Predicate description generation batch_69fe59d03a648190bbe846cb5730a477 completed May 8, 2026, 9:46 p.m.
Created at: May 1, 2026, 1:30 a.m.