Triple
T2753640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snyder |
E61047
|
entity |
| Predicate | isOccupationalFormOf |
P41655
|
FINISHED |
| Object | 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: tailor | Statement: [Snyder, isOccupationalFormOf, tailor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOccupationalFormOf Context triple: [Snyder, isOccupationalFormOf, tailor]
-
A.
occupationalNameFor
Indicates that one entity is the name or label used to denote the occupation or profession of another entity.
-
B.
derivesFromOccupation
Indicates that one entity originates from, is obtained through, or is a result of another entity’s occupation or professional role.
-
C.
isAssociatedWithProfessionOfBearer
Indicates that one entity is connected to, or involved with, the profession or occupational role held by another entity.
-
D.
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).
-
E.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
- F. None of above. chosen
Provenance (4 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb6ed9c08190824d1866e198ef80 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd91497ec8190927e91ad33549eda |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:56 p.m.