Triple
T858537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYSE National |
E18547
|
entity |
| Predicate | orderMatching |
P20244
|
FINISHED |
| Object | price-time priority |
—
|
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: price-time priority | Statement: [NYSE National, orderMatching, price-time priority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderMatching Context triple: [NYSE National, orderMatching, price-time priority]
-
A.
orderType
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
B.
order
Indicates that one entity requests, arranges, or directs that another entity provide a good, service, or action, typically in a specified sequence or priority.
-
C.
orderFoundedBy
Indicates that a particular order or organization was established or created by a specific person or entity.
-
D.
orderEstablished
Indicates that a formal sequence or arrangement between entities has been created and set as the authoritative or agreed-upon order.
-
E.
orderFounded
Indicates that an organization or group was established or created at a specific time or by a specific entity.
- F. None of above. chosen
Provenance (4 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac4f740881909cb59a6c18a77af3 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab498bb0819080e3afb684b504b6 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.