Triple
T1505803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rick Hahn |
E33897
|
entity |
| Predicate | typeOfOccupation |
P2374
|
FINISHED |
| Object | front office executive |
—
|
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: front office executive | Statement: [Rick Hahn, typeOfOccupation, front office executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfOccupation Context triple: [Rick Hahn, typeOfOccupation, front office executive]
-
A.
subjectOccupation
chosen
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
B.
vocationType
Indicates the specific kind or category of occupation, profession, or calling associated with an entity.
-
C.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
D.
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).
-
E.
requiredOccupationOf
Indicates that one entity specifies the occupation or job role that is required or expected for another entity (such as a position, task, or qualification).
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90584b8b881908e112c7e59163812 |
completed | March 5, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69a88727ce48819089b482cdc25453d1 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:24 p.m.