Triple
T35292293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helena Rozhenko |
E1019259
|
entity |
| Predicate | parentalRoleToWorf |
P18066
|
FINISHED |
| Object | nurturing |
—
|
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: nurturing | Statement: [Helena Rozhenko, parentalRoleToWorf, nurturing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentalRoleToWorf Context triple: [Helena Rozhenko, parentalRoleToWorf, nurturing]
-
A.
parentalRoleTo
chosen
Indicates a parental relationship in which one entity holds a parent role with respect to another entity.
-
B.
offspringRole
Indicates that an entity participates in a parent–child relationship specifically in the role of the offspring (child/descendant) relative to another entity.
-
C.
motherRole
Indicates that one entity holds the role or function of a mother in relation to another entity.
-
D.
fatherCultureRole
Indicates that one culture assumes a paternal or fatherly role in relation to another culture.
-
E.
paterPatratusRole
Indicates the role of someone formally appointed as pater patratus, the official representative empowered to speak or act on behalf of a group in a ritual or diplomatic context.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 3, 2026, 4:03 p.m.