Triple
T25064698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SREN |
E627752
|
entity |
| Predicate | associatedCompanyStockExchangeAbbreviation |
P48660
|
FINISHED |
| Object | SIX |
—
|
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: SIX | Statement: [SREN, associatedCompanyStockExchangeAbbreviation, SIX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCompanyStockExchangeAbbreviation Context triple: [SREN, associatedCompanyStockExchangeAbbreviation, SIX]
-
A.
underlyingCompanyExchange
Indicates that one entity is the stock exchange on which the underlying company of another financial instrument or contract is listed or traded.
-
B.
issuerStockExchangeCode
chosen
Indicates the stock exchange code where the issuer’s securities are listed or traded.
-
C.
underlyingCompanyStockExchangeCountry
Indicates the country in which the stock exchange is located on which the underlying company’s shares are traded.
-
D.
hasStockExchange
Indicates that an entity is associated with or listed on a particular stock exchange.
-
E.
underlyingCompanyExchangeCode
Indicates the stock exchange code on which the underlying company’s securities are listed or traded.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 18, 2026, 6:10 a.m.