Triple
T17005854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLASS Act |
E412567
|
entity |
| Predicate | implementationDecision |
P2165
|
FINISHED |
| Object | deemed actuarially unsustainable |
—
|
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: deemed actuarially unsustainable | Statement: [CLASS Act, implementationDecision, deemed actuarially unsustainable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementationDecision Context triple: [CLASS Act, implementationDecision, deemed actuarially unsustainable]
-
A.
decisionImplementedBy
Indicates that a particular decision is carried out, executed, or put into effect by a specified agent or entity.
-
B.
decisionMaking
Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
-
C.
makesDecisionBy
Indicates that one entity determines or chooses an outcome, course of action, or judgment by means of another entity, method, or process.
-
D.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
-
E.
decisionType
chosen
Indicates the specific category or nature of a decision associated with an entity or event.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d3831268819089286053a5acf653 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.