Triple

T36657740
Position Surface form Disambiguated ID Type / Status
Subject Pelóri E905037 entity
Predicate inUniverseEventAssociation P47960 FINISHED
Object Hiding of Valinor 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: Hiding of Valinor | Statement: [Pelóri, inUniverseEventAssociation, Hiding of Valinor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inUniverseEventAssociation
Context triple: [Pelóri, inUniverseEventAssociation, Hiding of Valinor]
  • A. inUniverseEvent chosen
    Indicates that an event occurs within, and is governed by the context or rules of, a particular fictional or defined universe.
  • B. inUniverseRaceAssociation
    Indicates an association where an entity is linked to a specific race or species within a particular fictional or defined universe.
  • C. inUniverseActivity
    Indicates that an activity or event occurs within the fictional universe or narrative world of a work, rather than outside it (e.g., in real life or meta-context).
  • D. inUniverseReference
    Indicates that one entity makes a reference to another entity that exists within the same fictional or conceptual universe.
  • E. associatedUniverse
    Indicates that one entity is linked or belongs to a particular universe, realm, or overarching world context.
  • 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_69f76e6e3b908190970251b30f76ad71 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fd49f6dbac81909744373a357b7982 completed May 8, 2026, 2:27 a.m.
PD Predicate disambiguation batch_69fd48ed68f481908374183c66a6b055 completed May 8, 2026, 2:22 a.m.
Created at: May 3, 2026, 4:11 p.m.