Triple
T25985549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasdaq Global Select Market |
E646190
|
entity |
| Predicate | hasListingCategoryCode |
P51031
|
FINISHED |
| Object | G |
—
|
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: G | Statement: [Nasdaq Global Select Market, hasListingCategoryCode, G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasListingCategoryCode Context triple: [Nasdaq Global Select Market, hasListingCategoryCode, G]
-
A.
haveCategoryCode
chosen
Indicates that an entity is associated with a specific classification or category identified by a code.
-
B.
hasListingAuthority
Indicates that an entity has the official power or permission to create, approve, or manage listings for another entity or resource.
-
C.
hasParentListing
Indicates that an item or listing is associated with a higher-level or primary listing from which it derives or to which it belongs.
-
D.
hasListingSystem
Indicates that an entity is associated with or uses a particular system or mechanism for listing or cataloging items, entries, or information.
-
E.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 22, 2026, 8:55 a.m.