Triple
T35753554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYSE:TTM |
E1033379
|
entity |
| Predicate | underlyingNSETicker |
P33802
|
FINISHED |
| Object | TATAMOTORS |
—
|
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: TATAMOTORS | Statement: [NYSE:TTM, underlyingNSETicker, TATAMOTORS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingNSETicker Context triple: [NYSE:TTM, underlyingNSETicker, TATAMOTORS]
-
A.
underlyingCompanyTicker
Indicates that one entity is the stock ticker symbol corresponding to the underlying company of another financial instrument or entity.
-
B.
hasUnderlyingExchangeTicker
Indicates that one financial instrument is based on, or derives its value from, another instrument identified by a specific exchange ticker.
-
C.
underlyingTickerCountryCode
Indicates the country code associated with the underlying ticker to which an instrument or contract is linked.
-
D.
tickerSymbol
Indicates the association between a financial instrument or company and its unique abbreviated code used for trading on a securities exchange.
-
E.
underlyingCompanyPrimaryListingTicker
chosen
Indicates the stock ticker symbol of the primary exchange listing for the underlying company.
- 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_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:06 p.m.