Triple
T17552613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anbang Insurance Group |
E427505
|
entity |
| Predicate | dateOfTakeover |
P2754
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Anbang Insurance Group, dateOfTakeover, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfTakeover Context triple: [Anbang Insurance Group, dateOfTakeover, 2018]
-
A.
timeOfMergerOrAcquisition
Indicates the specific point in time when a merger or acquisition event occurs between entities.
-
B.
deFactoTransferDate
Indicates the date on which control or ownership is effectively transferred in practice, regardless of the formal or legal transfer date.
-
C.
acquisitionDate
chosen
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
D.
divestitureDate
Indicates the date on which an entity formally disposes of, sells, or otherwise relinquishes ownership or control of an asset, business unit, or investment.
-
E.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4561fcaf48190b2e45b77e5ff7d0f |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.