Triple
T2970721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archipelago Exchange |
E80272
|
entity |
| Predicate | hadTradingVenueType |
P42396
|
FINISHED |
| Object | order-driven market |
—
|
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: order-driven market | Statement: [Archipelago Exchange, hadTradingVenueType, order-driven market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadTradingVenueType Context triple: [Archipelago Exchange, hadTradingVenueType, order-driven market]
-
A.
hasTradingVenueType
chosen
Indicates the specific category or type of trading venue associated with a given trading platform or marketplace.
-
B.
tradedOn
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
C.
hasTradingFloor
Indicates that an entity operates or contains a physical or virtual trading floor where financial instruments are actively bought and sold.
-
D.
hasElectronicTradingSystem
Indicates that an entity operates or utilizes an electronic system for executing trades or transactions.
-
E.
hasTrade
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
- 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9973ed6881908f11f49ca2e171df |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.