Triple
T24764408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperador Inc. |
E619539
|
entity |
| Predicate | acquisitionOfWhyteAndMackayDate |
P15703
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Emperador Inc., acquisitionOfWhyteAndMackayDate, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionOfWhyteAndMackayDate Context triple: [Emperador Inc., acquisitionOfWhyteAndMackayDate, 2014]
-
A.
acquisitionCompletedYear
chosen
Indicates the calendar year in which an acquisition transaction was fully completed.
-
B.
acquiredFranchiseYear
Indicates the year in which an entity obtained ownership or control of a franchise.
-
C.
acquisitionDate
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
D.
timeOfMergerOrAcquisition
Indicates the specific point in time when a merger or acquisition event occurs between entities.
-
E.
acquisitionAgreementYear
Indicates the calendar year in which an acquisition agreement between entities was made or came into effect.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:28 a.m.