Triple
T5090154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tomb of Joseph of Arimathea |
E114732
|
entity |
| Predicate | ownerRole |
P60670
|
FINISHED |
| Object | member of the Sanhedrin |
—
|
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: member of the Sanhedrin | Statement: [tomb of Joseph of Arimathea, ownerRole, member of the Sanhedrin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerRole Context triple: [tomb of Joseph of Arimathea, ownerRole, member of the Sanhedrin]
-
A.
ownerPosition
Indicates the spatial or positional relationship of an owner relative to the owned entity.
-
B.
hasCapitalOwnerRole
Indicates that an entity holds the role or status of owning capital in relation to another entity or asset.
-
C.
accessRole
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
-
D.
ownerOrFounder
Indicates that an entity either owns or has founded another entity, capturing both ownership and founding relationships.
-
E.
ordinationRole
Indicates the specific religious or ceremonial office, function, or capacity in which an entity is formally ordained.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75407e6881908d00377a256ff37e |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd72b8d7a88190ad53fae64f17e22c |
completed | March 20, 2026, 4:15 p.m. |
Created at: March 20, 2026, 1:40 p.m.