Triple
T4768360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michal |
E105865
|
entity |
| Predicate | childlessness |
P40543
|
FINISHED |
| Object | had no child to the day of her death |
—
|
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: had no child to the day of her death | Statement: [Michal, childlessness, had no child to the day of her death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: childlessness Context triple: [Michal, childlessness, had no child to the day of her death]
-
A.
fertility
Indicates the capacity or potential of an entity to reproduce or generate offspring.
-
B.
fertilityStatus
Indicates the reproductive condition or capability of an entity, such as whether it is fertile, infertile, or at a particular stage of fertility.
-
C.
hasFertility
Indicates that one entity possesses or exhibits the capacity to reproduce or generate offspring.
-
D.
hadNoSurvivingChildren
chosen
Indicates that the person did not have any children who were alive at the relevant point in time.
-
E.
reproductiveFeature
Indicates a relationship where an entity possesses or is characterized by a particular reproductive trait, structure, or capability.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6537eb80819096e0ae906c59d605 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.