Triple
T32800937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kabuyutan |
E838893
|
entity |
| Predicate | hasCustodian |
P20855
|
FINISHED |
| Object | traditional religious leader |
—
|
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: traditional religious leader | Statement: [kabuyutan, hasCustodian, traditional religious leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustodian Context triple: [kabuyutan, hasCustodian, traditional religious leader]
-
A.
hasCustodyRole
chosen
Indicates that one entity holds a specific custodial responsibility or role in relation to another entity.
-
B.
hasKeyCustodians
Indicates that certain entities are responsible for holding, managing, or safeguarding specific keys for another entity or resource.
-
C.
hasEstateManager
Indicates that an entity is responsible for managing, overseeing, or administering the estate or property of another entity.
-
D.
holderIs
Indicates that one entity serves as the holder, possessor, or container of another entity.
-
E.
hasSettlor
Indicates that an entity serves as the settlor (the person or party who creates or settles a trust) in relation to a given trust or legal arrangement.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 1, 2026, 1:14 a.m.