Triple
T50725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam Stock Exchange |
E994
|
entity |
| Predicate | openOutcryTrading |
P1802
|
FINISHED |
| Object | historically used |
—
|
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: historically used | Statement: [Amsterdam Stock Exchange, openOutcryTrading, historically used]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openOutcryTrading Context triple: [Amsterdam Stock Exchange, openOutcryTrading, historically used]
-
A.
marketPosition
Indicates the relative standing or rank an entity holds within a specific market compared to its competitors.
-
B.
hasStockExchange
Indicates that an entity is associated with or listed on a particular stock exchange.
-
C.
orderType
chosen
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
D.
openingLine
Indicates that one entity is the first line or initial statement that begins another entity, such as a text, speech, or conversation.
-
E.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24ba7016481909d595402712db6e2 |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac23f04819080cef9365ed990d4 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.