Triple
T23420331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RRIF |
E560631
|
entity |
| Predicate | governingLegislationLevel |
P6712
|
FINISHED |
| Object | Federal tax 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: Federal tax law | Statement: [RRIF, governingLegislationLevel, Federal tax law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingLegislationLevel Context triple: [RRIF, governingLegislationLevel, Federal tax law]
-
A.
governingBodyLevel
Indicates the hierarchical level or tier at which a governing body operates within a political or organizational structure.
-
B.
levelOfGovernment
Indicates the specific tier or layer within a governmental hierarchy (e.g., local, regional, national) at which an entity operates or an action is taken.
-
C.
legalAuthorityLevel
Indicates the degree or rank of formal legal power or jurisdiction an entity holds in relation to another or within a given context.
-
D.
jurisdictionLevel
chosen
Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
-
E.
typeOfLegislation
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
- 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_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. |
Created at: April 17, 2026, 5:44 p.m.