Triple
T8709038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stuart Ullman |
E206725
|
entity |
| Predicate | hiresForPosition |
P26127
|
FINISHED |
| Object | winter caretaker of the Overlook Hotel |
—
|
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: winter caretaker of the Overlook Hotel | Statement: [Stuart Ullman, hiresForPosition, winter caretaker of the Overlook Hotel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiresForPosition Context triple: [Stuart Ullman, hiresForPosition, winter caretaker of the Overlook Hotel]
-
A.
canHire
Indicates that one entity has the authority or ability to employ or recruit another entity.
-
B.
personReferredToPosition
Indicates that one entity has been mentioned or cited as a candidate or occupant for a particular role, job, or position.
-
C.
offeredPosition
chosen
Indicates that one entity has extended a job or role opportunity to another entity.
-
D.
namedForEmployer
Indicates that an entity is named after, or in honor of, its employer.
-
E.
appointmentRequirement
Indicates that a particular action, service, or interaction can only occur if an appointment has been scheduled or a specified appointment condition is met.
- 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c2e9c688190aceefaa2c3b7d7bd |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.