Triple
T10415653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athene Holding Ltd. |
E245506
|
entity |
| Predicate | typicalProductType |
P90900
|
FINISHED |
| Object | fixed indexed 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 indexed annuities | Statement: [Athene Holding Ltd., typicalProductType, fixed indexed annuities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProductType Context triple: [Athene Holding Ltd., typicalProductType, fixed indexed annuities]
-
A.
typeOfProducts
chosen
Indicates the kinds or categories of products that are associated with or offered by an entity.
-
B.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an entity.
-
C.
typicalSupportedUnitType
Indicates the kind or category of unit that an entity is normally designed or expected to support.
-
D.
typicalGadgets
Indicates that the associated items are commonly used or standard gadgets typically found or expected in a given context.
-
E.
appliesToProductType
Indicates that something (such as a rule, offer, or condition) is relevant or applicable specifically to a certain type or category of product.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea108fec8190819423630888fa2b |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:10 p.m.