Triple
T22757985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nowakówna |
E562903
|
entity |
| Predicate | familyRelationshipIndication |
P89441
|
FINISHED |
| Object | daughter |
—
|
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: daughter | Statement: [Nowakówna, familyRelationshipIndication, daughter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyRelationshipIndication Context triple: [Nowakówna, familyRelationshipIndication, daughter]
-
A.
politicalRelationship
Indicates a relationship in which entities are connected through political roles, alliances, affiliations, or interactions within a political context.
-
B.
relationshipToParents
Indicates the type or nature of a person's familial relationship to their parents.
-
C.
familyRelationNote
Indicates a descriptive note or annotation that provides additional context or clarification about a specified family relationship between entities.
-
D.
familyConnectionTo
chosen
Indicates a familial relationship or bond that exists between two entities, such as by blood, marriage, or adoption.
-
E.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a7a8ca481909953dcd6fbcc5fcf |
completed | April 29, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:25 p.m.