Triple

T36547828
Position Surface form Disambiguated ID Type / Status
Subject sinking of Beleriand E901180 entity
Predicate consequenceForElves P124166 FINISHED
Object many Elves depart to Aman LITERAL 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: many Elves depart to Aman | Statement: [sinking of Beleriand, consequenceForElves, many Elves depart to Aman]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consequenceForElves
Context triple: [sinking of Beleriand, consequenceForElves, many Elves depart to Aman]
  • A. consideredByElves
    Indicates that something is regarded, judged, or held in a particular way by elves.
  • B. mythologicalConsequence chosen
    Indicates a causal or resultant relationship where one entity brings about, embodies, or suffers a consequence within a mythological or legendary narrative context.
  • C. consequenceOfQuest
    Indicates that an event, state, or outcome occurs as a direct result of completing or progressing in a specific quest.
  • D. houseElfRightsActivist
    Indicates advocacy or activism in support of rights, fair treatment, and improved conditions for house elves.
  • E. consequenceOfInfluence
    Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
  • 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_69f76e61217081908b79d610fe67b013 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fcc4b700748190ae00b21d09c96695 completed May 7, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69fcb0f9d3d881908a049475182fb039 completed May 7, 2026, 3:34 p.m.
Created at: May 3, 2026, 4:11 p.m.