Triple
T642306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYSE Arca |
E16764
|
entity |
| Predicate | supportsOrderTypes |
P9835
|
FINISHED |
| Object | limit orders |
—
|
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: limit orders | Statement: [NYSE Arca, supportsOrderTypes, limit orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOrderTypes Context triple: [NYSE Arca, supportsOrderTypes, limit orders]
-
A.
orderTypesSupported
chosen
Indicates that a system or entity supports specific types or categories of orders that can be placed or processed.
-
B.
orderType
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
C.
canOrder
Indicates that one entity has the ability or permission to place an order for another entity or item.
-
D.
supportsAddressTypes
Indicates that an entity is capable of handling or working with one or more specified types of addresses.
-
E.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f03db7481909e49c325c5f7cdae |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0830008190a26ee158ed4dd1fe |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.