Triple

T9777243
Position Surface form Disambiguated ID Type / Status
Subject Battle of Helm's Deep E237277 entity
Predicate inUniverseTime P47717 FINISHED
Object 3rd Age of Middle-earth — 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: 3rd Age of Middle-earth | Statement: [Battle of Helm's Deep, inUniverseTime, 3rd Age of Middle-earth]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inUniverseTime
Context triple: [Battle of Helm's Deep, inUniverseTime, 3rd Age of Middle-earth]
  • A. inUniverseDate
    Indicates that an entity is associated with or occurs on a specific date within a fictional or defined universe’s internal timeline.
  • B. inUniverse
    Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
  • C. inUniverseAge chosen
    Indicates the age of an entity as measured within the timeline or continuity of a specific fictional or defined universe.
  • D. inUniverseType
    Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
  • E. 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).
  • 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_69ca84d975a08190aab25b02a89bdab3 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda133ef548190aaecdf49de9c5aa8 completed April 1, 2026, 10:50 p.m.
PD Predicate disambiguation batch_69cd03d3b68c81909e570401a891b9f2 completed April 1, 2026, 11:38 a.m.
Created at: March 30, 2026, 8:26 p.m.