Triple

T13810879
Position Surface form Disambiguated ID Type / Status
Subject Thora Birch E331885 entity
Predicate givenName P17 FINISHED
Object Thora E672600 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: Thora | Statement: [Thora Birch, givenName, Thora]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thora
Context triple: [Thora Birch, givenName, Thora]
  • A. Thora
    Thora is a small rural locality in New South Wales, Australia, situated in the Bellingen Valley near the Bellinger River.
  • B. Atlakviða
    Atlakviða is an Old Norse heroic poem from the Poetic Edda that recounts the tragic betrayal and violent downfall of the Burgundian (Gjúkungar) kings at the hands of Atli.
  • C. Skaði
    Skaði is a giantess and goddess in Norse mythology associated with skiing, winter, and mountains, known for her marriage to the god Njord.
  • D. Þór
    Þór is the Old Norse thunder god of Norse mythology, known for wielding the hammer Mjölnir and protecting gods and humans from giants.
  • E. Hulda chosen
    Hulda is a feminine given name of Germanic origin, historically used in Scandinavian and German-speaking countries.
  • 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_69d81c59f8808190a851bc56afdc55e9 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de026ff6b481908066d6bf27064417 completed April 14, 2026, 9:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7b09161108190abbd97a30af9ab49 completed May 3, 2026, 8:31 p.m.
Created at: April 9, 2026, 10:12 p.m.