Triple

T37552469
Position Surface form Disambiguated ID Type / Status
Subject Ranger-General of Silvermoon E933618 entity
Predicate isLinkedToFaction P25766 FINISHED
Object Alliance (historically, via high elves) 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: Alliance (historically, via high elves) | Statement: [Ranger-General of Silvermoon, isLinkedToFaction, Alliance (historically, via high elves)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isLinkedToFaction
Context triple: [Ranger-General of Silvermoon, isLinkedToFaction, Alliance (historically, via high elves)]
  • A. hasFaction chosen
    Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
  • B. hasOpposingFaction
    Indicates that one faction stands in opposition or conflict to another faction.
  • C. factionAssociated
    Indicates that an entity is connected to, aligned with, or belongs to a particular faction.
  • D. associatedWithDynastyOrFaction
    Indicates that an entity is linked to, belongs to, or is significantly connected with a particular dynasty or faction.
  • E. foughtForFaction
    Indicates that an entity actively participated in or supported a particular faction, typically in a conflict or struggle.
  • 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_69f76eca55bc8190acf25741793d5dac completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbb084760c8190a1554985d3c3cb7a completed May 6, 2026, 9:20 p.m.
PD Predicate disambiguation batch_69fbadf3cb548190ba3b7514f76b790a completed May 6, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:17 p.m.