Triple
T24950053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Bendigo |
E624302
|
entity |
| Predicate | canHaveOccupation |
P105981
|
FINISHED |
| Object | Anglican bishop |
—
|
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: Anglican bishop | Statement: [Bishop of Bendigo, canHaveOccupation, Anglican bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHaveOccupation Context triple: [Bishop of Bendigo, canHaveOccupation, Anglican bishop]
-
A.
hasOccupationInWork
Indicates that an entity holds or performs a specific occupation within a particular work, project, or creative production.
-
B.
hasTypicalOccupation
Indicates that an entity commonly or characteristically works in a particular job or profession.
-
C.
hasOccupationInferred
Indicates that an entity is inferred, rather than explicitly stated, to have a particular occupation or professional role.
-
D.
holderIsOccupation
chosen
Indicates that the holder entity has the specified occupation or job role.
-
E.
hasPastOccupation
Indicates that an entity previously held a particular job, role, or occupation in the past.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f423ff8a448190bacc4e8ff2e20e1a |
completed | May 1, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:56 a.m.