Triple
T30603919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lillo Brancato |
E778983
|
entity |
| Predicate | occupationAfterRelease |
P75487
|
FINISHED |
| Object | actor |
—
|
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: actor | Statement: [Lillo Brancato, occupationAfterRelease, actor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupationAfterRelease Context triple: [Lillo Brancato, occupationAfterRelease, actor]
-
A.
resumedOccupation
Indicates that an entity has returned to and continued a previous occupation or role after a period of interruption or absence.
-
B.
employedAfter
Indicates that one entity became employed by another entity at a point in time later than a referenced employment event or period.
-
C.
memberLaterOccupation
chosen
Indicates that an individual later held a particular occupation or position after an earlier point in time or role.
-
D.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
-
E.
occupationEnd
Indicates the point in time or event at which an entity’s role, job, or position comes to an end.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 8:25 p.m.