Triple
T24131998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ken Jenkins |
E597978
|
entity |
| Predicate | notableCharacterEmployer |
P89211
|
FINISHED |
| Object | Sacred Heart Hospital |
—
|
NE NERFINISHED |
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: Sacred Heart Hospital | Statement: [Ken Jenkins, notableCharacterEmployer, Sacred Heart Hospital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterEmployer Context triple: [Ken Jenkins, notableCharacterEmployer, Sacred Heart Hospital]
-
A.
notableCharacterOccupation
Indicates that a notable character is associated with a specific occupation or professional role.
-
B.
notableEmployer
Indicates that an entity has been employed by, or has worked for, a particularly significant or noteworthy organization or individual.
-
C.
notableWorkCharacter
Indicates that a character appears in, is associated with, or plays a role in a particular notable work.
-
D.
employerOfNotablePerson
chosen
Indicates that an entity serves or has served as the employer of a person who is considered notable.
-
E.
associatedCompanyNotableRole
Indicates that an entity has a notable role or position in a specified associated company.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df78b6f08190809fc154110fa201 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:25 p.m.