Triple

T24046309
Position Surface form Disambiguated ID Type / Status
Subject Cornelis Sandvoort E595528 entity
Predicate familyGoal P154658 FINISHED
Object to secure a lineage LITERAL 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: to secure a lineage | Statement: [Cornelis Sandvoort, familyGoal, to secure a lineage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: familyGoal
Context triple: [Cornelis Sandvoort, familyGoal, to secure a lineage]
  • A. familyAspect
    Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
  • B. family
    Indicates a familial relationship or connection between entities, such as being related by blood, marriage, or adoption.
  • C. familyContext
    Indicates that the entities are related or associated within a family or household context, such as kinship, caregiving, or shared domestic life.
  • D. familyAlliance
    Indicates a cooperative or supportive relationship formed between families, often involving mutual obligations, shared interests, or joint actions.
  • E. familyInvolvement
    Indicates that there is participation, engagement, or influence of family members in the context of a particular activity, decision, or situation.
  • F. None of above. chosen

Provenance (4 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_69e288c06a908190899cad4531f32c9a completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1d9ca5a18819086da68b69eed8cc1 completed April 29, 2026, 10:13 a.m.
PD Predicate disambiguation batch_69f1764345388190a3102b62ddb729b4 completed April 29, 2026, 3:08 a.m.
PDg Predicate description generation batch_69f1785afe3c81909be28986ffe944bf completed April 29, 2026, 3:17 a.m.
Created at: April 17, 2026, 10:15 p.m.