Triple
T23967109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasdaq Capital Market |
E604115
|
entity |
| Predicate | isTier |
P47925
|
FINISHED |
| Object | entry-level Nasdaq listing tier |
—
|
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: entry-level Nasdaq listing tier | Statement: [Nasdaq Capital Market, isTier, entry-level Nasdaq listing tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTier Context triple: [Nasdaq Capital Market, isTier, entry-level Nasdaq listing tier]
-
A.
hasUpperTier
Indicates that one entity occupies a higher or superior level, rank, or layer in a hierarchical structure relative to another entity.
-
B.
isRank
chosen
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
-
C.
partOfTier
Indicates that one entity belongs to, is included within, or forms a component of a specified tier or level in a hierarchical structure.
-
D.
hadTierSystem
Indicates that an entity implemented or used a structured tier-based system, typically organizing elements into hierarchical levels or ranks.
-
E.
hasTierStructure
Indicates that something is organized into distinct hierarchical levels or layers within a structured system.
- 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.