Triple
T18876683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OMX Copenhagen 25 |
E461705
|
entity |
| Predicate | dataVendorCode |
P508
|
FINISHED |
| Object | OMXC25 |
—
|
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: OMXC25 | Statement: [OMX Copenhagen 25, dataVendorCode, OMXC25]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OMXC25 Context triple: [OMX Copenhagen 25, dataVendorCode, OMXC25]
-
A.
OMXC25
chosen
OMXC25 is the leading stock market index of the Copenhagen Stock Exchange, tracking the performance of the 25 most traded Danish blue-chip companies.
-
B.
OMXC20
OMXC20 is the main stock market index of the Copenhagen Stock Exchange, tracking the performance of 20 of its most traded companies.
-
C.
OMXC
OMXC is a Danish stock market index that tracks the performance of all shares listed on the Nasdaq Copenhagen exchange.
-
D.
OMX
OMX is the stock ticker symbol for OfficeMax, a former American office supplies retail chain.
-
E.
OMXH
OMXH is the stock market index and trading symbol associated with Nasdaq Helsinki, representing Finnish equities listed on the exchange.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3cf0aa0819090991fc9e14910fb |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 10, 2026, 11:57 a.m.