Triple
T30726699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NXPI |
E782295
|
entity |
| Predicate | underlyingCompanyCEOStartYear |
P53318
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [NXPI, underlyingCompanyCEOStartYear, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingCompanyCEOStartYear Context triple: [NXPI, underlyingCompanyCEOStartYear, 2020]
-
A.
CEOStartYear
chosen
Indicates the calendar year in which an individual began serving as CEO of an organization.
-
B.
underlyingCompanyCEOAtFormation
Indicates that a person was the CEO of the underlying company at the time the company was formed.
-
C.
hasUnderlyingCompanyCEO
Indicates that a specified company has a particular person serving as its Chief Executive Officer (CEO) at a fundamental or primary organizational level.
-
D.
underlyingCompanyFormationYear
Indicates the calendar year in which the referenced underlying company was originally formed or established.
-
E.
notableOfficeStartYear
Indicates the calendar year in which an entity began serving in a particular notable office or position.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 29, 2026, 8:37 p.m.