Triple
T5687873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramgarhia Punjabis |
E125355
|
entity |
| Predicate | occupationalSpecialization |
P41655
|
FINISHED |
| Object | woodwork |
—
|
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: woodwork | Statement: [Ramgarhia Punjabis, occupationalSpecialization, woodwork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupationalSpecialization Context triple: [Ramgarhia Punjabis, occupationalSpecialization, woodwork]
-
A.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
B.
positionSpecialization
Indicates that one position is a more specialized or focused variant of another, broader position.
-
C.
isOccupationalFormOf
chosen
Indicates that one occupation is a specific form, variant, or specialization of another, more general occupation.
-
D.
occupationalNameFor
Indicates that one entity is the name or label used to denote the occupation or profession of another entity.
-
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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.