Triple
T34435980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HHLA |
E883954
|
entity |
| Predicate | stockExchangeSegment |
P64613
|
FINISHED |
| Object | Prime Standard |
—
|
NE NERFINISHED |
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: Prime Standard | Statement: [HHLA, stockExchangeSegment, Prime Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stockExchangeSegment Context triple: [HHLA, stockExchangeSegment, Prime Standard]
-
A.
tradingSegment
chosen
Indicates that one entity operates within, or is associated with, a specific trading segment or market subdivision for transactional activities.
-
B.
stockExchangeParent
Indicates that one stock exchange serves as the parent or primary governing entity of another stock exchange.
-
C.
stockExchangeContext
Indicates a relationship or action occurring within the context of a stock exchange, such as trading, listing, or pricing of financial instruments.
-
D.
stockExchangeStatus
Indicates the operational or trading condition of a stock exchange at a given time (e.g., open, closed, halted).
-
E.
mainStockExchangeOf
Indicates that one entity serves as the primary stock exchange on which the other entity (typically a company or financial instrument) is chiefly listed or traded.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.