Triple
T24388307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA board of directors |
E614809
|
entity |
| Predicate | overseesTicker |
P156017
|
FINISHED |
| Object | NASDAQ:NVDA |
—
|
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: NASDAQ:NVDA | Statement: [NVIDIA board of directors, overseesTicker, NASDAQ:NVDA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesTicker Context triple: [NVIDIA board of directors, overseesTicker, NASDAQ:NVDA]
-
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.
succeededByTicker
Indicates that one entity is directly followed or replaced by another entity in a sequence of ticker symbols.
-
C.
oversee
Indicates having responsibility for supervising, directing, or managing the actions or work of another entity.
-
D.
hasTickerType
Indicates that an entity is associated with a specific type or category of ticker (e.g., stock, index, or other financial instrument ticker).
-
E.
hasTickerRoot
Indicates that an entity’s ticker symbol is derived from, or based on, the specified root string.
- F. None of above. chosen
Provenance (4 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29456cc548190bb92b750fd2d04af |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:03 a.m.