Triple

T27554521
Position Surface form Disambiguated ID Type / Status
Subject Erendis E695594 entity
Predicate authorialSource P177520 FINISHED
Object The History of Middle-earth (draft materials) 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: The History of Middle-earth (draft materials) | Statement: [Erendis, authorialSource, The History of Middle-earth (draft materials)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: authorialSource
Context triple: [Erendis, authorialSource, The History of Middle-earth (draft materials)]
  • A. originalAuthorOfSource
    Indicates that an entity is the original creator or author of a given source or work.
  • B. originAuthor
    Indicates that an entity is the original creator or author of another entity (such as a work, document, or idea).
  • C. bookAuthorOfSource
    Indicates that a book serves as the authorial source from which the referenced content, work, or information is derived.
  • D. canonicalAuthor
    Indicates that an entity is the officially recognized or standard author of a given work or resource.
  • E. editorialSource
    Indicates that one entity serves as the editorial origin, provider, or authority for the content or information associated with 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_69ef5387e97c8190a9dab040d21cd048 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f7009d39508190af7301f824615e88 completed May 3, 2026, 8 a.m.
PD Predicate disambiguation batch_69f6fc53f4f881908dcc698687bbb64d completed May 3, 2026, 7:42 a.m.
PDg Predicate description generation batch_69f6ffb7554881908993d6d2ffbcf8f5 completed May 3, 2026, 7:56 a.m.
Created at: April 27, 2026, 1:36 p.m.