Triple
T24265361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oslo Stock Exchange |
E604823
|
entity |
| Predicate | primaryMarketOf |
P28886
|
FINISHED |
| Object | Norway |
—
|
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: Norway | Statement: [Oslo Stock Exchange, primaryMarketOf, Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMarketOf Context triple: [Oslo Stock Exchange, primaryMarketOf, Norway]
-
A.
primaryListingMarket
Indicates the market or exchange where a security is first and principally listed for trading.
-
B.
parentMarket
Indicates that one market serves as the higher-level or containing market in which another market is nested or from which it is derived.
-
C.
coreMarket
chosen
Indicates that an entity serves as the primary or most important market for another entity’s products, services, or activities.
-
D.
referenceMarket
Indicates that one entity serves as the benchmark or primary comparison market used to evaluate, price, or contextualize another entity.
-
E.
marketedFor
Indicates that something is promoted, advertised, or positioned as being intended or suitable for a particular use, audience, or purpose.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6b32108190856be036ac9cfced |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.