Triple
T23967090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasdaq Capital Market |
E604115
|
entity |
| Predicate | hasListingStandardsType |
P43031
|
FINISHED |
| Object | financial standards |
—
|
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: financial standards | Statement: [Nasdaq Capital Market, hasListingStandardsType, financial standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasListingStandardsType Context triple: [Nasdaq Capital Market, hasListingStandardsType, financial standards]
-
A.
hasAssociatedStandard
Indicates that something is linked to or governed by a particular standard or set of standards.
-
B.
hasListingAuthority
Indicates that an entity has the official power or permission to create, approve, or manage listings for another entity or resource.
-
C.
hasListingSystem
Indicates that an entity is associated with or uses a particular system or mechanism for listing or cataloging items, entries, or information.
-
D.
standardsType
chosen
Indicates the classification or category of standards that apply to or are associated with an entity or activity.
-
E.
standardsUsedIn
Indicates that certain standards are applied, referenced, or followed within a particular context, process, or entity.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1d8cc2881909ac2c46030677e9f |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:24 p.m.