Triple
T10415648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athene Holding Ltd. |
E245506
|
entity |
| Predicate | isMajorPlatformFor |
P11917
|
FINISHED |
| Object | insurance solutions |
—
|
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: insurance solutions | Statement: [Athene Holding Ltd., isMajorPlatformFor, insurance solutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorPlatformFor Context triple: [Athene Holding Ltd., isMajorPlatformFor, insurance solutions]
-
A.
consideredPlatform
Indicates that one entity is regarded or treated as a platform (e.g., a base, medium, or environment) for another entity or activity.
-
B.
hasPrimaryPlatform
chosen
Indicates that one entity is designated as the main or principal platform associated with another entity.
-
C.
typicalPlatform
Indicates that something commonly or usually serves as the platform or environment on which another thing operates, appears, or is based.
-
D.
isMultiplatform
Indicates that something is designed to operate or be available across multiple platforms or environments.
-
E.
platformUsed
Indicates that an action, event, or interaction was carried out using a particular platform (e.g., software, service, or system) as the medium or tool.
- 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.