Triple
T38308920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | onsemi |
E1033630
|
entity |
| Predicate | hasSECFilingsUnder |
P50792
|
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, hasSECFilingsUnder, ON]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSECFilingsUnder Context triple: [onsemi, hasSECFilingsUnder, ON]
-
A.
hasSECFilingsUnderTicker
chosen
Indicates that an entity has SEC filings associated with a specific stock ticker symbol.
-
B.
hasSECFilingsURL
Indicates that there is a URL linking an entity to its filings or disclosure documents submitted to the U.S. Securities and Exchange Commission (SEC).
-
C.
SECSubmission
Indicates the act of formally filing or delivering required documents or reports to the U.S. Securities and Exchange Commission (SEC) for regulatory review or disclosure.
-
D.
hasFinancialStatements
Indicates that an entity possesses or is associated with one or more formal financial statements documenting its financial performance or position.
-
E.
mainRegulatoryFiling
Indicates that a given document or submission serves as the primary regulatory filing associated with an entity or activity.
- 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_6a00ccadb6908190ab810a7c05315fa8 |
completed | May 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_6a00cc0f86b88190a0d2c43618558f86 |
completed | May 10, 2026, 6:18 p.m. |
Created at: May 3, 2026, 4:30 p.m.