Triple
T23420321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RRIF |
E560631
|
entity |
| Predicate | isCreditorProtected |
P152207
|
FINISHED |
| Object | Sometimes, subject to provincial law |
—
|
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: Sometimes, subject to provincial law | Statement: [RRIF, isCreditorProtected, Sometimes, subject to provincial law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCreditorProtected Context triple: [RRIF, isCreditorProtected, Sometimes, subject to provincial law]
-
A.
isProtectedFor
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
B.
isProtectedFrom
Indicates that one entity is safeguarded or shielded against harm, damage, or adverse effects caused by another entity or factor.
-
C.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
D.
hasMainCreditorType
Indicates the primary category or type of creditor that holds the main claim or financial interest in relation to an entity.
-
E.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54605dc81909aad9834ef6ff8a1 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:44 p.m.