Triple
T7461128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Series EE savings bond |
E176250
|
entity |
| Predicate | finalMaturity |
P7920
|
FINISHED |
| Object | 30 years |
—
|
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: 30 years | Statement: [Series EE savings bond, finalMaturity, 30 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalMaturity Context triple: [Series EE savings bond, finalMaturity, 30 years]
-
A.
maturityDuration
Indicates the length of time required for something to reach its full development, readiness, or maturity.
-
B.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
C.
maximumBondMaturity
chosen
Indicates the longest allowable or actual time period until a bond tied to an entity reaches its maturity date.
-
D.
maturityType
Indicates the kind or category of maturity associated with an entity, such as how or when an obligation, product, or process reaches its full or due state.
-
E.
mustBeMaturedIn
Indicates that something is required to undergo a maturation process within a specified context, condition, or environment before it is considered ready or valid.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d6cf8c8190a31cac121d151d78 |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:38 p.m.