Triple
T27175535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina 401(k) and 457 retirement savings plans |
E683033
|
entity |
| Predicate | componentPlan |
P29774
|
FINISHED |
| Object | North Carolina 401(k) Plan |
—
|
NE NERFINISHED |
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: North Carolina 401(k) Plan | Statement: [North Carolina 401(k) and 457 retirement savings plans, componentPlan, North Carolina 401(k) Plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentPlan Context triple: [North Carolina 401(k) and 457 retirement savings plans, componentPlan, North Carolina 401(k) Plan]
-
A.
plannedComponent
Indicates that one entity is intended or scheduled to serve as a component or part of another entity in a planned or future configuration.
-
B.
implementedPlan
Indicates that a specific plan has been carried out or put into effect by an entity.
-
C.
partOfPlan
chosen
Indicates that one entity is included as a component or step within a broader plan or strategy.
-
D.
platformPlanned
Indicates that a platform is intended or scheduled to be created, implemented, or made available in the future.
-
E.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 9:25 a.m.