Triple

T7055455
Position Surface form Disambiguated ID Type / Status
Subject Abraham Rycken E164076 entity
Predicate familyName P18 FINISHED
Object Rycken E121603 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: Rycken | Statement: [Abraham Rycken, familyName, Rycken]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rycken
Context triple: [Abraham Rycken, familyName, Rycken]
  • A. Rycken chosen
    Rycken is a Dutch-origin surname historically borne by families such as that of Abraham Rycken in the Low Countries and early colonial America.
  • B. Rombaken
    Rombaken is a fjord in northern Norway, known as an inner branch of the Ofotfjord near the town of Narvik.
  • C. Raskens
    Raskens is a novel by Swedish author Vilhelm Moberg that portrays the harsh life and inner struggles of a 19th-century Swedish soldier and farmer.
  • D. Rayak
    Rayak is a town in Lebanon known historically for its strategic railway junction and air base in the Bekaa Valley.
  • E. Ryhall
    Ryhall is a village and civil parish in the South Kesteven district of Lincolnshire, England, known for its historic church and rural character.
  • 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_69c68861678881909961ddf4d779f750 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e267664c81909501feb12683a002 completed March 27, 2026, 8:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7889ddd488190b1e55828909133eb completed March 28, 2026, 7:51 a.m.
Created at: March 27, 2026, 2:38 p.m.