Triple
T33210926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Zinc |
E850154
|
entity |
| Predicate | leavesJobType |
P176192
|
FINISHED |
| Object | high-pressure corporate law firm |
—
|
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: high-pressure corporate law firm | Statement: [David Zinc, leavesJobType, high-pressure corporate law firm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leavesJobType Context triple: [David Zinc, leavesJobType, high-pressure corporate law firm]
-
A.
leavesEmployer
Indicates that an employee ends or terminates their working relationship with an employer.
-
B.
leaveType
Indicates the type or category of leave associated with an absence or time-off event (e.g., vacation, sick leave, parental leave).
-
C.
employmentType
Indicates the specific kind or category of employment relationship that exists between an individual and an employer (e.g., full-time, part-time, contract).
-
D.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
E.
typeOfOccupationEnded
Indicates that a particular type of occupation or job role has come to an end for an entity.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6dd3b335481909e24d4eb5b0269f9 |
completed | May 3, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:30 a.m.