Triple
T13184082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US0846701086 |
E313801
|
entity |
| Predicate | hasUnderlyingSecurityType |
P67141
|
FINISHED |
| Object | Common stock |
—
|
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: Common stock | Statement: [US0846701086, hasUnderlyingSecurityType, Common stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnderlyingSecurityType Context triple: [US0846701086, hasUnderlyingSecurityType, Common stock]
-
A.
hasUnderlyingIssuer
Indicates that one entity serves as the fundamental or primary issuer behind another entity, such as a financial instrument or structured product.
-
B.
hasUnderlyingMarket
Indicates that one entity is based on, derives its value from, or is traded with reference to another entity that serves as its fundamental market.
-
C.
underlyingConstituentsType
Indicates the type or category of fundamental components that make up or underlie a given entity or structure.
-
D.
hasUnderlyingLEI
Indicates that an entity is associated with, or identified by, a specific underlying Legal Entity Identifier (LEI).
-
E.
hasFinancialInstrumentType
chosen
Indicates that an entity is associated with, or classified by, a specific type or category of financial instrument.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:15 p.m.