Triple

T9840009
Position Surface form Disambiguated ID Type / Status
Subject Sebastian Stark E239196 entity
Predicate familyName P18 FINISHED
Object Stark E149830 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: Stark | Statement: [Sebastian Stark, familyName, Stark]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stark
Context triple: [Sebastian Stark, familyName, Stark]
  • A. Stark chosen
    Stark is a common surname of Scottish origin associated with various notable figures in politics, science, and popular culture.
  • B. Stange
    Stange is a rural municipality in Innlandet county, Norway, known for its agricultural landscape and proximity to the town of Hamar.
  • C. Stahl
    Stahl is a surname of German origin borne by various notable individuals across fields such as sports, politics, and the arts.
  • D. Henry Stark
    Henry Stark is a notable individual who shares the Stark surname, which is associated with several prominent historical and cultural figures.
  • E. Steele
    Steele is a surname most notably borne by Charles Steele Jr., an American civil rights leader and former president of the Southern Christian Leadership Conference.
  • 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_69ca84e3f0c48190ada72a65ebd50efd completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb34b045481908f89abd576aab497 completed April 2, 2026, 12:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1e429682c8190a94339b96d4081f6 completed April 5, 2026, 4:25 a.m.
Created at: March 30, 2026, 8:33 p.m.