Triple
T5066254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Tallinn |
E114150
|
entity |
| Predicate | listedOn |
P1278
|
FINISHED |
| Object | Nasdaq Tallinn |
E284653
|
NE 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: Nasdaq Tallinn | Statement: [Port of Tallinn, listedOn, Nasdaq Tallinn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nasdaq Tallinn Context triple: [Port of Tallinn, listedOn, Nasdaq Tallinn]
-
A.
Nasdaq Copenhagen
Nasdaq Copenhagen is Denmark’s primary securities exchange, where shares of major Danish companies such as Danske Bank are listed and traded.
-
B.
Nasdaq Helsinki
Nasdaq Helsinki is Finland’s primary stock exchange, hosting the trading of major Finnish companies and other securities.
-
C.
Nasdaq Nordic
chosen
Nasdaq Nordic is a regional stock exchange group that operates several securities markets across the Nordic and Baltic countries under the Nasdaq brand.
-
D.
Nasdaq Stockholm
Nasdaq Stockholm is Sweden’s primary stock exchange, hosting the trading of shares in major Swedish and Nordic companies.
-
E.
Nasdaq INET
Nasdaq INET is Nasdaq’s high-performance electronic trading platform used across several of its exchanges to match and process securities orders.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd749aceac8190817278266308fd64 |
completed | March 20, 2026, 4:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bea49d917081909ead17eed3f8af90 |
completed | March 21, 2026, 2:01 p.m. |
Created at: March 20, 2026, 1:38 p.m.