Triple
T30444825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishvar Darji |
E774546
|
entity |
| Predicate | conversionOfOccupation |
P119450
|
FINISHED |
| Object | from tanner to tailor |
—
|
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: from tanner to tailor | Statement: [Ishvar Darji, conversionOfOccupation, from tanner to tailor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionOfOccupation Context triple: [Ishvar Darji, conversionOfOccupation, from tanner to tailor]
-
A.
convertedToOccupation
chosen
Indicates that an entity changed or transitioned from a previous role or status into a specified occupation.
-
B.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
C.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
-
D.
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.
-
E.
derivesFromOccupation
Indicates that one entity originates from, is obtained through, or is a result of another entity’s occupation or professional role.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 29, 2026, 8:08 p.m.