Triple
T21938682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramgarhia |
E541758
|
entity |
| Predicate | occupationalIdentity |
P2374
|
FINISHED |
| Object | skilled tradespeople |
—
|
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: skilled tradespeople | Statement: [Ramgarhia, occupationalIdentity, skilled tradespeople]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupationalIdentity Context triple: [Ramgarhia, occupationalIdentity, skilled tradespeople]
-
A.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
-
B.
natureOfOccupation
Indicates the type or character of a person's occupation, describing what kind of work or role it is rather than who performs it.
-
C.
occupationalNameFor
Indicates that one entity is the name or label used to denote the occupation or profession of another entity.
-
D.
subjectOccupation
chosen
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
E.
isOccupationalFormOf
Indicates that one occupation is a specific form, variant, or specialization of another, more general occupation.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1241f582c81909a244419cec38b19 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:55 p.m.