Triple
T35753553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYSE:TTM |
E1033379
|
entity |
| Predicate | underlyingBSETicker |
P74237
|
FINISHED |
| Object | 500570 |
—
|
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: 500570 | Statement: [NYSE:TTM, underlyingBSETicker, 500570]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingBSETicker Context triple: [NYSE:TTM, underlyingBSETicker, 500570]
-
A.
hasUnderlyingExchangeTicker
chosen
Indicates that one financial instrument is based on, or derives its value from, another instrument identified by a specific exchange ticker.
-
B.
underlyingCompanyTicker
Indicates that one entity is the stock ticker symbol corresponding to the underlying company of another financial instrument or entity.
-
C.
underlyingTickerCountryCode
Indicates the country code associated with the underlying ticker to which an instrument or contract is linked.
-
D.
hasExchangeTicker
Indicates that an entity is identified or listed under a specific ticker symbol on a particular financial exchange.
-
E.
BITCdisplayedAs
Indicates that one entity is visually presented or rendered in the form or style of another entity.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:06 p.m.