Triple

T14706387
Position Surface form Disambiguated ID Type / Status
Subject House Greyjoy E345439 entity
Predicate ancestralLands P90583 FINISHED
Object Great Wyk E1114236 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: Great Wyk | Statement: [House Greyjoy, ancestralLands, Great Wyk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Great Wyk
Context triple: [House Greyjoy, ancestralLands, Great Wyk]
  • A. Great Wyk chosen
    Great Wyk is the largest and one of the most prominent of the Iron Islands in George R.R. Martin’s A Song of Ice and Fire series.
  • B. Wyke
    Wyke is a village and suburb in the metropolitan borough of Bradford, West Yorkshire, England.
  • C. Hythe
    Hythe is a small village in northwestern Alberta, Canada, situated west of the city of Grande Prairie.
  • D. Hythe
    Hythe is a historic coastal town in Kent, England, known as one of the original Cinque Ports that once played a key role in maritime defense and trade.
  • E. Gunnerside
    Gunnerside is a small rural village in the Yorkshire Dales of northern England, known for its scenic Swaledale setting and historic lead-mining heritage.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d822e4a8c08190a155df736bb7bc13 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb6086c608190a66c64e23a3e002f completed April 14, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdfb8221a4819098937018f24a0b44 completed May 8, 2026, 3:04 p.m.
Created at: April 10, 2026, 1:28 a.m.