Triple

T35481960
Position Surface form Disambiguated ID Type / Status
Subject House Blackfyre E1025492 entity
Predicate originCountryInUniverse P82660 FINISHED
Object Westeros E68957 NE 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: Westeros | Statement: [House Blackfyre, originCountryInUniverse, Westeros]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: originCountryInUniverse
Context triple: [House Blackfyre, originCountryInUniverse, Westeros]
  • A. countryOfOriginFictional chosen
    Indicates that a fictional work, character, or element originates from or is associated with a particular country within its narrative or setting.
  • B. creationCountry
    Indicates the country in which an entity was originally created, produced, or brought into existence.
  • C. countryOfFictionalContext
    Indicates that a work of fiction is primarily set in, or contextually associated with, a particular country.
  • D. laterCountryOfOrigin
    Indicates that an entity’s country of origin changed, and this predicate specifies the country that became its origin at a later time than a previously associated country.
  • E. countryOfFictionalEmpire
    Indicates the real-world country in which a fictional empire is located, originates, or is primarily associated.
  • F. None of above.

Provenance (4 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_69f76dfadba0819083456aadcd6864ea completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_6a037c8d06cc8190ab6a5e18d9d2571e completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a384a2b313c8190a43ffe2a714bdf62 completed June 21, 2026, 8:31 p.m.
PD Predicate disambiguation batch_6a037a0324d08190ac5b610cc0f6a38c completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:04 p.m.