Triple
T29324856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabinowitz |
E743612
|
entity |
| Predicate | isOccupationallyDerived |
P127286
|
FINISHED |
| Object | rabbi |
—
|
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: rabbi | Statement: [Rabinowitz, isOccupationallyDerived, rabbi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOccupationallyDerived Context triple: [Rabinowitz, isOccupationallyDerived, rabbi]
-
A.
isOccupationalInOrigin
chosen
Indicates that something (typically a name or term) originates from or is derived from an occupation or profession.
-
B.
isOccupationalFormOf
Indicates that one occupation is a specific form, variant, or specialization of another, more general occupation.
-
C.
derivesFromOccupation
Indicates that one entity originates from, is obtained through, or is a result of another entity’s occupation or professional role.
-
D.
isOccupationalSurname
Indicates that a surname originates from or is derived from a person’s occupation or trade.
-
E.
hasOccupationInferred
Indicates that an entity is inferred, rather than explicitly stated, to have a particular 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66894ce4c8190b1104ea889b98a8e |
completed | May 2, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:25 p.m.