Triple
T30407252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | renBCH |
E773511
|
entity |
| Predicate | custodyModel |
P169184
|
FINISHED |
| Object | decentralized custody via RenVM |
—
|
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: decentralized custody via RenVM | Statement: [renBCH, custodyModel, decentralized custody via RenVM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: custodyModel Context triple: [renBCH, custodyModel, decentralized custody via RenVM]
-
A.
custody
Indicates having legal responsibility and authority over the care and control of another entity, typically a child or dependent.
-
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.
hasCustodyRole
Indicates that one entity holds a specific custodial responsibility or role in relation to another entity.
-
D.
intendedCustodyLevel
Indicates the custody or security level that is planned or designated for an entity, rather than the level currently in effect.
-
E.
heldByFamilyUntil
Indicates that something remained in the possession or care of a family up to a specified point in time.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686204b2c8190afea8470275fd875 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:04 p.m.