Triple

T38463111
Position Surface form Disambiguated ID Type / Status
Subject Alliance of Lordaeron E912498 entity
Predicate primaryMemberRace P86582 FINISHED
Object humans 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: humans | Statement: [Alliance of Lordaeron, primaryMemberRace, humans]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryMemberRace
Context triple: [Alliance of Lordaeron, primaryMemberRace, humans]
  • A. primaryRace chosen
    Indicates the main racial or ethnic category with which an entity is primarily identified or classified.
  • B. traditionalMemberRace
    Indicates that an entity belongs to a race or ethnic group that is traditionally associated with or historically characteristic of a particular membership or community.
  • C. previousPrimaryRace
    Indicates that one race event is the immediately preceding primary race relative to another race in a sequence or schedule.
  • D. primaryRaceType
    Indicates the main or predominant race category associated with an entity, as opposed to any secondary or additional race classifications.
  • E. relatedRace
    Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
  • 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_69f76e861d8c81908559031dc66e3c15 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a037c903be48190a2fafa53d7d50d42 completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a1e32108190897356d6a7fed879 completed May 12, 2026, 7:06 p.m.
Created at: May 3, 2026, 4:31 p.m.