Triple
T36691298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conner Peripherals |
E905962
|
entity |
| Predicate | formerListedExchange |
P56915
|
FINISHED |
| Object | NASDAQ |
—
|
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: NASDAQ | Statement: [Conner Peripherals, formerListedExchange, NASDAQ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerListedExchange Context triple: [Conner Peripherals, formerListedExchange, NASDAQ]
-
A.
formerListedCompany
Indicates that an entity was previously listed on a stock exchange but is no longer publicly traded there.
-
B.
formerlyListedOn
chosen
Indicates that an entity was previously listed on a particular exchange, registry, or listing platform but is no longer listed there.
-
C.
stockExchangeListingSuccessor
Indicates that one entity has succeeded or replaced another in being listed on a particular stock exchange.
-
D.
ownerStockExchangeListing
Indicates that a stock exchange on which an entity is listed is owned or operated by another entity.
-
E.
canBeListedOnStockExchange
Indicates that an entity meets the necessary conditions to be eligible for listing and trading on a stock exchange.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00ac5654a0819090701f61a5802d64 |
completed | May 10, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_6a00ab94b5e881909e15d1342e5f43be |
completed | May 10, 2026, 4 p.m. |
Created at: May 3, 2026, 4:12 p.m.