Triple
T9289061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stock Exchange Electronic Trading Service |
E223469
|
entity |
| Predicate | matchingMechanism |
P83596
|
FINISHED |
| Object | electronic order book |
—
|
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: electronic order book | Statement: [Stock Exchange Electronic Trading Service, matchingMechanism, electronic order book]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchingMechanism Context triple: [Stock Exchange Electronic Trading Service, matchingMechanism, electronic order book]
-
A.
matches
Indicates that two entities correspond to or are in agreement with each other according to some defined criteria or pattern.
-
B.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
C.
matchSystem
chosen
Indicates a relationship where an entity is paired or aligned with a particular system according to defined matching criteria.
-
D.
matchTypes
Indicates that two or more entities share the same type or category according to a specified classification.
-
E.
matchStructure
Indicates that two entities share the same structural pattern or organization, regardless of their specific content or values.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0862b34c819097cb7c1777313925 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.