Triple
T30662465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tapestry, Inc. |
E780567
|
entity |
| Predicate | isListedCompanyOn |
P23592
|
FINISHED |
| Object | New York Stock Exchange |
—
|
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: New York Stock Exchange | Statement: [Tapestry, Inc., isListedCompanyOn, New York Stock Exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isListedCompanyOn Context triple: [Tapestry, Inc., isListedCompanyOn, New York Stock Exchange]
-
A.
hasListedCompany
Indicates that an entity owns, controls, or is associated with a company that is publicly listed on a stock exchange.
-
B.
canBeListedOnStockExchange
Indicates that an entity meets the necessary conditions to be eligible for listing and trading on a stock exchange.
-
C.
isListed
Indicates that an entity appears on or is included in a specified list, registry, or catalog.
-
D.
isListedSecurityOf
chosen
Indicates that one entity is a security (such as a stock or bond) that is officially listed and traded on the other entity, which is a financial exchange or trading venue.
-
E.
parentCompanyListedOn
Indicates that the parent company of an entity is publicly listed on a particular stock exchange or market.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68ae1d64481908f63a8c1393cd4dd |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:31 p.m.