Triple
T6539939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasdaq Global Market |
E168258
|
entity |
| Predicate | dataVendorCodeContext |
P19199
|
FINISHED |
| Object | Nasdaq-listed securities |
—
|
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: Nasdaq-listed securities | Statement: [Nasdaq Global Market, dataVendorCodeContext, Nasdaq-listed securities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataVendorCodeContext Context triple: [Nasdaq Global Market, dataVendorCodeContext, Nasdaq-listed securities]
-
A.
dataVendor
Indicates a relationship where one entity serves as a provider or supplier of data to another entity.
-
B.
hasDataVendorCode
chosen
Indicates that an entity is associated with a specific vendor-assigned code used to identify its data source or provider.
-
C.
dataVendorSymbol
Indicates a mapping between a data vendor and the specific symbol or code they use to identify an asset or item.
-
D.
dataVendorName
Indicates the name or identifier of the vendor that supplies or provides the data.
-
E.
catalogCode
Indicates that an entity is assigned a specific catalog identifier or code used for classification or reference.
- 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_69c68a51564081909e93aee0dbd9cca3 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:50 p.m.