Triple

T17251717
Position Surface form Disambiguated ID Type / Status
Subject Skaro E418769 entity
Predicate hasPart P35 FINISHED
Object Halldon E418769 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: Halldon | Statement: [Skaro, hasPart, Halldon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Halldon
Context triple: [Skaro, hasPart, Halldon]
  • A. Halldon chosen
    Halldon is a fictional continent on the planet Skaro in the Doctor Who universe, known as part of the Daleks’ homeworld geography.
  • B. Danderhall
    Danderhall is a village in Midlothian, Scotland, situated just southeast of Edinburgh and functioning largely as a commuter community for the city.
  • C. Hiorthhamn
    Hiorthhamn is a former mining settlement on the island of Spitsbergen in the Svalbard archipelago, now largely abandoned and known for its historical remains in the Arctic landscape.
  • D. Wulfhall
    Wulfhall is a historic English manor in Wiltshire best known as the ancestral home of the Seymour family, including Jane Seymour, third wife of King Henry VIII.
  • E. Ellendun
    Ellendun was an early medieval English settlement best known as the site of a pivotal 9th-century battle that helped shift the balance of power among the Anglo-Saxon kingdoms.
  • 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_69d886d9ab108190b70edd8d17aa1204 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42e694f788190a1c86e95264ed2fe completed April 19, 2026, 1:22 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0170fb89248190ae431ce51dfeaffd completed May 11, 2026, 6:02 a.m.
Created at: April 10, 2026, 5:39 a.m.