Triple
T26057351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adrian Dolan |
E657155
|
entity |
| Predicate | leavesReason |
P15987
|
FINISHED |
| Object | to enter witness protection |
—
|
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: to enter witness protection | Statement: [Adrian Dolan, leavesReason, to enter witness protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leavesReason Context triple: [Adrian Dolan, leavesReason, to enter witness protection]
-
A.
coveredReasonForLeave
Indicates that a specified reason for leave is included under and qualifies for coverage within a particular leave policy or program.
-
B.
reasonForLeaving
chosen
Indicates the cause, motivation, or circumstance that led an entity to depart or discontinue an association, position, or place.
-
C.
leaveType
Indicates the type or category of leave associated with an absence or time-off event (e.g., vacation, sick leave, parental leave).
-
D.
leaves
Indicates that an entity departs from or goes away from another entity, location, or situation.
-
E.
leavesEmployer
Indicates that an employee ends or terminates their working relationship with an employer.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6068fa9708190a061497990b64cd4 |
completed | May 2, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 7:12 p.m.