Triple
T34223944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DEO |
E877996
|
entity |
| Predicate | underlyingExchangeCountryCode |
P145238
|
FINISHED |
| Object | US |
—
|
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: US | Statement: [DEO, underlyingExchangeCountryCode, US]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingExchangeCountryCode Context triple: [DEO, underlyingExchangeCountryCode, US]
-
A.
underlyingTickerCountryCode
Indicates the country code associated with the underlying ticker to which an instrument or contract is linked.
-
B.
underlyingCompanyStockExchangeCountry
chosen
Indicates the country in which the stock exchange is located on which the underlying company’s shares are traded.
-
C.
underlyingExchangeMIC
Indicates the Market Identifier Code (MIC) of the exchange on which the referenced instrument or trade is fundamentally listed or executed.
-
D.
issuerStockExchangeCountry
Indicates the country in which the stock exchange listing the issuer’s securities is located.
-
E.
underlyingCompanyExchange
Indicates that one entity is the stock exchange on which the underlying company of another financial instrument or contract is listed or traded.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 1, 2026, 1:55 a.m.