Triple
T26596096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevron Canada |
E667493
|
entity |
| Predicate | hasParentStockExchangeListing |
P179465
|
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: [Chevron Canada, hasParentStockExchangeListing, New York Stock Exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentStockExchangeListing Context triple: [Chevron Canada, hasParentStockExchangeListing, New York Stock Exchange]
-
A.
hasStockExchange
Indicates that an entity is associated with or listed on a particular stock exchange.
-
B.
stockExchangeListingOfSubsidiary
Indicates that a subsidiary company is listed and traded on a particular stock exchange.
-
C.
canBeListedOnStockExchange
Indicates that an entity meets the necessary conditions to be eligible for listing and trading on a stock exchange.
-
D.
ownerStockExchangeListing
Indicates that a stock exchange on which an entity is listed is owned or operated by another entity.
-
E.
hasUnderlyingCompanyPrimaryListing
Indicates that an entity is associated with the company where that company’s primary stock exchange listing is held.
- F. None of above. chosen
Provenance (4 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 27, 2026, 2:10 a.m.