Triple
T10273083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bani Shaiba family |
E240887
|
entity |
| Predicate | typeOfCustodianship |
P20855
|
FINISHED |
| Object | ceremonial custodianship |
—
|
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: ceremonial custodianship | Statement: [Bani Shaiba family, typeOfCustodianship, ceremonial custodianship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCustodianship Context triple: [Bani Shaiba family, typeOfCustodianship, ceremonial custodianship]
-
A.
hasCustodyRole
chosen
Indicates that one entity holds a specific custodial responsibility or role in relation to another entity.
-
B.
sharesCustodyWith
Indicates that two or more parties jointly hold legal responsibility and decision-making authority for the care and upbringing of the same dependent, typically a child.
-
C.
typeOfTrust
Indicates the specific kind or category of trust that characterizes the relationship between entities.
-
D.
intendedCustodyLevel
Indicates the custody or security level that is planned or designated for an entity, rather than the level currently in effect.
-
E.
typeOfRight
Indicates the specific category or nature of a right that is held, exercised, or assigned in a given context.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d288acf48190bbf14a5cb2dfe1f4 |
completed | April 7, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ef6e6c81908a8ee52e4d28127b |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:36 a.m.