Triple
T6556398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oslo Stock Exchange |
E152459
|
entity |
| Predicate | openedForStockTrading |
P67026
|
FINISHED |
| Object | 1881 |
—
|
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: 1881 | Statement: [Oslo Stock Exchange, openedForStockTrading, 1881]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForStockTrading Context triple: [Oslo Stock Exchange, openedForStockTrading, 1881]
-
A.
openedForTrade
chosen
Indicates that an entity has begun allowing commercial transactions or trading activities to occur.
-
B.
stockExchangeStatus
Indicates the operational or trading condition of a stock exchange at a given time (e.g., open, closed, halted).
-
C.
tradingStatus
Indicates the current state or condition of an entity’s ability to be traded or engaged in trading activities.
-
D.
hasTradingHours
Indicates that an entity operates or is available for trading during specified time periods.
-
E.
usedByStockExchange
Indicates that something (such as a system, standard, or instrument) is utilized or adopted by a stock exchange in its operations or services.
- 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_69c688058d6881908c19b309cc55dbfa |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.