Triple
T9938147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AET |
E194006
|
entity |
| Predicate | issuerOriginalBusiness |
P91260
|
FINISHED |
| Object | life insurance |
—
|
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: life insurance | Statement: [AET, issuerOriginalBusiness, life insurance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerOriginalBusiness Context triple: [AET, issuerOriginalBusiness, life insurance]
-
A.
issuerFormerParent
Indicates that the subject entity was formerly the parent (e.g., controlling or owning entity) of the issuer entity, but no longer holds that parent status.
-
B.
issuerOperatesIn
Indicates that an issuing entity conducts business activities or has operational presence within a specified geographic area or jurisdiction.
-
C.
issuerPosition
Indicates the role, rank, or job position held by the entity acting as the issuer in a given context.
-
D.
issuerBestKnownFor
Indicates the primary work, achievement, or characteristic for which an issuer is most widely recognized.
-
E.
issuerOwnsBusinessesIn
Indicates that the issuer owns one or more business entities that are located or operate within the specified place.
- F. None of above. chosen
Provenance (4 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5e64760819094f599f158d32f33 |
completed | April 2, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:44 p.m.