Triple
T7847469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 403(b) plan |
E181957
|
entity |
| Predicate | historicallyInvestedIn |
P17330
|
FINISHED |
| Object | fixed annuities |
—
|
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: fixed annuities | Statement: [403(b) plan, historicallyInvestedIn, fixed annuities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyInvestedIn Context triple: [403(b) plan, historicallyInvestedIn, fixed annuities]
-
A.
hasHistoricalHoldings
Indicates that an entity possesses or maintains items, records, or assets of historical significance.
-
B.
historicallyConcentratedIn
Indicates that something has been predominantly or densely present, active, or occurring within a particular place or group during past periods.
-
C.
investsIn
chosen
Indicates that one entity allocates resources, typically money or capital, into another entity with the expectation of future returns or benefits.
-
D.
historicallySoughtBy
Indicates that one entity has been actively pursued, desired, or searched for by another entity in the past.
-
E.
historicallySoughtAs
Indicates that one entity has been pursued, desired, or actively sought by another entity over a historical period or in past contexts.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb164105fc8190a60aaa27dd619d5a |
completed | March 31, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:49 p.m.