Triple
T21717228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CR (historical) |
E536060
|
entity |
| Predicate | underlyingCompanyAcquisitionYear |
P15703
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [CR (historical), underlyingCompanyAcquisitionYear, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingCompanyAcquisitionYear Context triple: [CR (historical), underlyingCompanyAcquisitionYear, 1999]
-
A.
acquisitionCompletedYear
chosen
Indicates the calendar year in which an acquisition transaction was fully completed.
-
B.
associatedCompanySpinOffYear
Indicates the year in which a related or associated company was spun off from its original parent organization.
-
C.
acquisitionAnnouncementYear
Indicates the calendar year in which an acquisition is publicly announced.
-
D.
acquisitionAgreementYear
Indicates the calendar year in which an acquisition agreement between entities was made or came into effect.
-
E.
hasUnderlyingCompanyIPOApproxYear
Indicates the approximate calendar year in which the underlying company completed its initial public offering (IPO).
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96babdc81908226ec043dbe7431 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.