Triple
T38310315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMD board of directors |
E1033663
|
entity |
| Predicate | governsCompanyType |
P118252
|
FINISHED |
| Object | public company |
—
|
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: public company | Statement: [AMD board of directors, governsCompanyType, public company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsCompanyType Context triple: [AMD board of directors, governsCompanyType, public company]
-
A.
companyTypeGoverned
chosen
Indicates that one entity has regulatory or governing authority over the type or classification of a company.
-
B.
governingCompany
Indicates that one company exercises control, authority, or management over another company.
-
C.
governsOfficeType
Indicates that an entity has authoritative control or regulatory oversight over a particular type or category of office.
-
D.
representsCompanyType
Indicates that an entity is associated with or classified under a specific type or category of company.
-
E.
underlyingCompanyType
Indicates the classification or category of company that forms the basis or source for another related entity or instrument.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.