Triple
T23003342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pieterssen |
E572690
|
entity |
| Predicate | denotesFamilyRelationship |
P94755
|
FINISHED |
| Object | descendant of Pieter |
—
|
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: descendant of Pieter | Statement: [Pieterssen, denotesFamilyRelationship, descendant of Pieter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesFamilyRelationship Context triple: [Pieterssen, denotesFamilyRelationship, descendant of Pieter]
-
A.
politicalRelationship
Indicates a relationship in which entities are connected through political roles, alliances, affiliations, or interactions within a political context.
-
B.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
-
C.
relationshipToRelative
chosen
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
D.
addressesRelationship
Indicates that one entity directs communication, remarks, or attention specifically toward another entity.
-
E.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
- F. None of above.
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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183549bdc81908fdcd44e2c92f7c4 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:50 p.m.