Triple
T38308919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | onsemi |
E1033630
|
entity |
| Predicate | ESGTicker |
P189993
|
FINISHED |
| Object | ON |
—
|
NE NERFINISHED |
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: ON | Statement: [onsemi, ESGTicker, ON]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ESGTicker Context triple: [onsemi, ESGTicker, ON]
-
A.
tickerFor
Indicates that one entity is the stock ticker symbol used to uniquely identify another entity (typically a publicly traded company or security) in financial markets.
-
B.
overseesTicker
Indicates that one entity has supervisory or managerial responsibility over the activities or status associated with a specific ticker symbol.
-
C.
isTickerFor
chosen
Indicates that one entity is the stock ticker symbol that uniquely represents another entity (such as a company or financial instrument) in trading contexts.
-
D.
timedEvent
Indicates that an event occurs within a specific time frame or is constrained by temporal conditions.
-
E.
timeSignalService
Indicates that one entity provides or is associated with a service that broadcasts or delivers time signals to others.
- 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_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.