Triple

T15759411
Position Surface form Disambiguated ID Type / Status
Subject Lucas Conijn E382053 entity
Predicate hasFamilyName P18 FINISHED
Object Conijn
Conijn is a Dutch surname of likely patronymic or toponymic origin borne by individuals such as Lucas Conijn.
 E1175178 NE FINISHED

How this triple was built (4 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: Conijn | Statement: [Lucas Conijn, hasFamilyName, Conijn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Conijn
Context triple: [Lucas Conijn, hasFamilyName, Conijn]
  • A. Woensel
    Woensel is a large residential district in the northern part of the Dutch city of Eindhoven, known for its diverse population and extensive post-war housing.
  • B. Kudelstaart
    Kudelstaart is a village in the Dutch province of North Holland, known for its location on the Westeinderplassen lake and its role in regional horticulture and water sports.
  • C. Brasschaat
    Brasschaat is a suburban municipality in northern Belgium known for its green residential character, parks, and proximity to the city of Antwerp.
  • D. Hondius
    Hondius is a Dutch family name most famously associated with Jodocus Hondius, a prominent 16th–17th century cartographer and engraver known for his influential maps and atlases.
  • E. Kanin
    Kanin is a surname most notably associated with American writer and director Garson Kanin.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Conijn
Triple: [Lucas Conijn, hasFamilyName, Conijn]
Generated description
Conijn is a Dutch surname of likely patronymic or toponymic origin borne by individuals such as Lucas Conijn.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Conijn
Target entity description: Conijn is a Dutch surname of likely patronymic or toponymic origin borne by individuals such as Lucas Conijn.
  • A. Woensel
    Woensel is a large residential district in the northern part of the Dutch city of Eindhoven, known for its diverse population and extensive post-war housing.
  • B. Kudelstaart
    Kudelstaart is a village in the Dutch province of North Holland, known for its location on the Westeinderplassen lake and its role in regional horticulture and water sports.
  • C. Brasschaat
    Brasschaat is a suburban municipality in northern Belgium known for its green residential character, parks, and proximity to the city of Antwerp.
  • D. Hondius
    Hondius is a Dutch family name most famously associated with Jodocus Hondius, a prominent 16th–17th century cartographer and engraver known for his influential maps and atlases.
  • E. Kanin
    Kanin is a surname most notably associated with American writer and director Garson Kanin.
  • F. None of above. chosen

Provenance (5 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_69d86d9e6b44819085d1f6a969ecb74c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e050b35ea48190a758ee76a57b5451 completed April 16, 2026, 3 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff8774eda08190a6231b4fd5027e6f completed May 9, 2026, 7:13 p.m.
NEDg Description generation batch_69ff885d33708190adb157afa7dc2e07 completed May 9, 2026, 7:17 p.m.
NED2 Entity disambiguation (via description) batch_69ff8948cc68819085c3953226236394 completed May 9, 2026, 7:21 p.m.
Created at: April 10, 2026, 4:47 a.m.