Triple
T13273537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYSE US equity market |
E316128
|
entity |
| Predicate | primaryTradingInstruments |
P67186
|
FINISHED |
| Object | common stock |
—
|
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: common stock | Statement: [NYSE US equity market, primaryTradingInstruments, common stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTradingInstruments Context triple: [NYSE US equity market, primaryTradingInstruments, common stock]
-
A.
tradeInstrument
Indicates a relationship where one entity is used as a financial or commercial instrument in a trade or transaction involving another entity.
-
B.
tradesInstrument
Indicates that one party engages in buying, selling, or exchanging a specified financial or tradable instrument.
-
C.
productsTraded
Indicates that one entity exchanges or deals specific goods or commodities with another entity.
-
D.
assetClassesTraded
chosen
Indicates that an entity trades, deals in, or is involved with specific categories or classes of financial assets.
-
E.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.