Triple
T27661184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZS |
E697125
|
entity |
| Predicate | tickerOnNASDAQ |
P6939
|
FINISHED |
| Object | ZS |
—
|
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: ZS | Statement: [ZS, tickerOnNASDAQ, ZS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tickerOnNASDAQ Context triple: [ZS, tickerOnNASDAQ, ZS]
-
A.
tickerSymbol
Indicates the association between a financial instrument or company and its unique abbreviated code used for trading on a securities exchange.
-
B.
stockExchangeStatus
Indicates the operational or trading condition of a stock exchange at a given time (e.g., open, closed, halted).
-
C.
tradedOn
chosen
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
D.
mainStockExchangeOf
Indicates that one entity serves as the primary stock exchange on which the other entity (typically a company or financial instrument) is chiefly listed or traded.
-
E.
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.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 2:36 p.m.