Triple
T5090153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tomb of Joseph of Arimathea |
E114732
|
entity |
| Predicate | ownerAffiliation |
P60669
|
FINISHED |
| Object | Jewish council |
—
|
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: Jewish council | Statement: [tomb of Joseph of Arimathea, ownerAffiliation, Jewish council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerAffiliation Context triple: [tomb of Joseph of Arimathea, ownerAffiliation, Jewish council]
-
A.
senderAffiliation
Indicates that the subject is institutionally or organizationally associated with the sender of a message or communication.
-
B.
administrativeAffiliation
Indicates that one entity is formally connected to, governed by, or overseen by another entity within an administrative or organizational structure.
-
C.
organizationAssociatedWith
Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
-
D.
primaryAffiliation
Indicates the main organization, institution, or group with which an entity is chiefly associated or formally connected.
-
E.
affiliateOfType
Indicates that an affiliate entity belongs to, or is categorized under, a specific type or classification.
- 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.