Triple
T34614318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Father |
E888820
|
entity |
| Predicate | hasParentalRoleFor |
P38221
|
FINISHED |
| Object | speaker |
—
|
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: speaker | Statement: [My Father, hasParentalRoleFor, speaker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentalRoleFor Context triple: [My Father, hasParentalRoleFor, speaker]
-
A.
hasFamilyRole
chosen
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
B.
hasParentalUnit
Indicates that an entity has a parent or guardian that serves as its primary caregiving or parental figure.
-
C.
isMotherOf
Indicates that one entity is the female parent who has given birth to or legally/ socially parents the other entity.
-
D.
hasParentAuthority
Indicates that one entity holds a higher-level or supervisory authority over another, similar to a parent organization’s control over a subordinate.
-
E.
parentageIncludes
Indicates that a given parentage or lineage set contains or encompasses a particular parent or ancestral relationship.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: May 1, 2026, 2:03 a.m.