Triple

T36843798
Position Surface form Disambiguated ID Type / Status
Subject Angmar War E910484 entity
Predicate involvesRealm P68119 FINISHED
Object Angmar 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: Angmar | Statement: [Angmar War, involvesRealm, Angmar]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: involvesRealm
Context triple: [Angmar War, involvesRealm, Angmar]
  • A. includesRealm chosen
    Indicates that one entity encompasses or contains a particular realm as part of its scope or domain.
  • B. concernsRealm
    Indicates that something is about or pertains specifically to a particular realm, domain, or sphere of activity or influence.
  • C. describesRealm
    Indicates that one entity provides a characterization, depiction, or account of the nature, features, or scope of another entity’s realm or domain.
  • D. residesInRealm
    Indicates that an entity lives or exists within a particular realm or domain.
  • E. overseesRealm
    Indicates that one entity has authority or supervisory control over a particular realm, domain, or territory.
  • 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_69f76e7f65a881908651b702da592b6d completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fe7b1c506c8190869c1a22031e0571 completed May 9, 2026, 12:09 a.m.
PD Predicate disambiguation batch_69fe796b2bdc8190a86980d44008f875 completed May 9, 2026, 12:01 a.m.
Created at: May 3, 2026, 4:13 p.m.