Triple
T15910636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WPO |
E385837
|
entity |
| Predicate | exchangeSymbolFormat |
P30804
|
FINISHED |
| Object | three-letter NYSE ticker |
—
|
LITERAL 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: three-letter NYSE ticker | Statement: [WPO, exchangeSymbolFormat, three-letter NYSE ticker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeSymbolFormat Context triple: [WPO, exchangeSymbolFormat, three-letter NYSE ticker]
-
A.
exchangeSymbol
Indicates that one entity serves as the ticker or trading symbol used to represent another entity on a specific exchange.
-
B.
exchangeSymbolType
chosen
Indicates the type or category of symbol used to represent an asset on a particular exchange.
-
C.
exchangeType
Indicates the kind or category of exchange occurring between entities, such as the method, direction, or nature of what is being traded or transferred.
-
D.
exchangeFormat
Indicates that one entity uses, supports, or is represented in a particular data or communication format for exchanging information with another system or entity.
-
E.
exchangeCurrency
Indicates a relationship where one party converts or trades an amount of one currency for an equivalent amount of another currency.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:52 a.m.