Triple
T32120282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UU. |
E820350
|
entity |
| Predicate | hasQuoteType |
P117833
|
FINISHED |
| Object | order-driven continuous trading |
—
|
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 continuous trading | Statement: [UU., hasQuoteType, order-driven continuous trading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuoteType Context triple: [UU., hasQuoteType, order-driven continuous trading]
-
A.
hasQuotationSystem
Indicates that an entity uses or is associated with a particular system or convention for representing quotations.
-
B.
hasQuotationStatus
Indicates that an entity has a particular quotation-related state or condition (such as being quoted, unquoted, or having a specific quotation status).
-
C.
containsQuotationMarks
Indicates that the referenced text includes one or more quotation mark characters within it.
-
D.
hasQuoteAssetClass
Indicates that something uses a particular asset class as the quote (pricing) side in a financial pair or instrument.
-
E.
quoteType
chosen
Indicates the specific category or classification of a quotation, such as its style, purpose, or contextual role in discourse.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:28 a.m.