Triple
T24407288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CGNU plc |
E615345
|
entity |
| Predicate | hasSuccessorCompany |
P6748
|
FINISHED |
| Object | Aviva plc |
—
|
NE NERFINISHED |
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: Aviva plc | Statement: [CGNU plc, hasSuccessorCompany, Aviva plc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorCompany Context triple: [CGNU plc, hasSuccessorCompany, Aviva plc]
-
A.
hasCorporateSuccessor
Indicates that one corporate entity is the legal successor to another, inheriting its rights, obligations, or continuity of business.
-
B.
succeededByCompanyName
chosen
Indicates that one company is followed or replaced by another company as its successor.
-
C.
associatedCompanyTickerSuccessor
Indicates that one company ticker symbol is the successor or replacement for another company ticker symbol in an association or mapping.
-
D.
successorManufacturer
Indicates that one manufacturer has taken over, replaced, or continued the role or operations of another manufacturer as its successor.
-
E.
hasBusinessSuccession
Indicates that one business entity continues, replaces, or inherits the operations, rights, or obligations of another business over time.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2957e8d5c8190bfed93aa308eb523 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.