Triple
T34224891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cooperage (historic) |
E878017
|
entity |
| Predicate | employedOccupation |
P2374
|
FINISHED |
| Object | coopers |
—
|
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: coopers | Statement: [Cooperage (historic), employedOccupation, coopers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedOccupation Context triple: [Cooperage (historic), employedOccupation, coopers]
-
A.
subjectOccupation
chosen
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
B.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
-
C.
occupationSetting
Indicates the typical environment or context in which an occupation is performed.
-
D.
employedRole
Indicates that an entity holds or performs a specific role or position within an employment or work context.
-
E.
employmentBasedCategory
Indicates that one entity’s classification or status is determined by its relationship to employment, such as being based on a specific job, role, or work-related category.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:55 a.m.