Triple
T7094008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family and Medical Leave Act of 1993 |
E165274
|
entity |
| Predicate | coveredReasonForLeave |
P74493
|
FINISHED |
| Object | birth of a child |
—
|
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: birth of a child | Statement: [Family and Medical Leave Act of 1993, coveredReasonForLeave, birth of a child]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredReasonForLeave Context triple: [Family and Medical Leave Act of 1993, coveredReasonForLeave, birth of a child]
-
A.
reasonForLeaving
Indicates the cause, motivation, or circumstance that led an entity to depart or discontinue an association, position, or place.
-
B.
reasonForWithdrawal
Indicates the cause, motive, or circumstance that explains why a withdrawal occurred.
-
C.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
D.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
-
E.
reasonForWork
Indicates that one entity specifies the motivation, cause, or purpose behind another entity’s work or activity.
- F. None of above. chosen
Provenance (4 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e55159848190a794ad77e60c5525 |
completed | March 27, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e24af9ac8190b24eee206ba8be36 |
completed | March 27, 2026, 8:02 p.m. |
Created at: March 27, 2026, 2:41 p.m.