Triple
T9763672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stryker Corporation |
E236728
|
entity |
| Predicate | tradesUnderTicker |
P1447
|
FINISHED |
| Object | SYK |
E236728
|
NE 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: SYK | Statement: [Stryker Corporation, tradesUnderTicker, SYK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SYK Context triple: [Stryker Corporation, tradesUnderTicker, SYK]
-
A.
SYK
chosen
SYK is the stock ticker symbol for Stryker Corporation, a major U.S.-based medical technology company specializing in surgical equipment, orthopedics, and related healthcare products.
-
B.
SYP
SYP is the ISO 4217 currency code for the Syrian pound, the official monetary unit of Syria.
-
C.
SY
SY is a UK postcode area covering Shrewsbury and surrounding parts of Shropshire and nearby counties in western England and the Welsh border region.
-
D.
SYR
SYR is the three-letter ISO 3166-1 alpha-3 country code representing the Middle Eastern nation of Syria.
-
E.
SYA
SYA is the three-letter National Rail station code for Styal railway station in Cheshire, England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda09d8bc88190808145f141b4a9f8 |
completed | April 1, 2026, 10:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1c412f0a48190b59d030b703a0e45 |
completed | April 5, 2026, 2:08 a.m. |
Created at: March 30, 2026, 8:25 p.m.