Triple
T23420297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RRIF |
E560631
|
entity |
| Predicate | predecessorAccountType |
P152198
|
FINISHED |
| Object | RRSP |
—
|
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: RRSP | Statement: [RRIF, predecessorAccountType, RRSP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAccountType Context triple: [RRIF, predecessorAccountType, RRSP]
-
A.
predecessorUser
Indicates that one user previously held a role, position, or state that is now held by another user, making the first user the predecessor of the second.
-
B.
predecessorSystemType
Indicates that one system type functioned as the predecessor or earlier version to another system type.
-
C.
predecessorRegimeType
Indicates the type of political regime that immediately governed before the current one.
-
D.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
E.
predecessorManagedBy
Indicates that a predecessor entity was managed, overseen, or administered by 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.