Triple
T30145791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VWAPY |
E766249
|
entity |
| Predicate | underlyingSecurityType |
P40808
|
FINISHED |
| Object | ordinary shares |
—
|
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: ordinary shares | Statement: [VWAPY, underlyingSecurityType, ordinary shares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingSecurityType Context triple: [VWAPY, underlyingSecurityType, ordinary shares]
-
A.
underlyingConstituentsType
Indicates the type or category of fundamental components that make up or underlie a given entity or structure.
-
B.
underlyingAsset
Indicates that one asset serves as the fundamental reference or basis for the value, performance, or contractual terms of another financial instrument or derivative.
-
C.
typeOfSecurityTraded
chosen
Indicates the specific kind or category of security that is being traded in a financial transaction.
-
D.
underlyingInstrument
Indicates that one financial instrument serves as the reference or basis for the value, payoff, or structure of another financial instrument.
-
E.
hasUnderlyingAssets
Indicates that one entity is supported, backed, or derived from another entity or set of entities that serve as its foundational assets.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 29, 2026, 7:18 p.m.