Triple
T5314482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maternity Allowance |
E119112
|
entity |
| Predicate | linkedLifeEvent |
P38165
|
FINISHED |
| Object | childbirth |
—
|
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: childbirth | Statement: [Maternity Allowance, linkedLifeEvent, childbirth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedLifeEvent Context triple: [Maternity Allowance, linkedLifeEvent, childbirth]
-
A.
partnerInLifeEvent
Indicates that two or more entities share a partnership or joint involvement in a specific life event or milestone.
-
B.
laterLifeEvent
Indicates that one event, condition, or action occurs during a later stage in an entity’s life relative to earlier life phases.
-
C.
notableEventInLife
Indicates that a particular event holds significant importance or impact within an entity’s life or personal history.
-
D.
familyEvent
chosen
Indicates a relationship where an event is organized around or significantly involves members of a family, such as gatherings, celebrations, or milestones.
-
E.
calendarLinkedTo
Indicates that one calendar is connected or synchronized with another calendar or calendaring system so that events or updates can be shared or reflected between them.
- 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_69bd446b57bc8190a513d2e6c40314f3 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:54 p.m.