Triple
T31021735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TradElect |
E790466
|
entity |
| Predicate | matchingAlgorithm |
P25130
|
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: [TradElect, matchingAlgorithm, price-time priority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchingAlgorithm Context triple: [TradElect, matchingAlgorithm, price-time priority]
-
A.
matchRatio
Indicates the degree of similarity or correspondence between two items, typically expressed as a numerical ratio or percentage.
-
B.
matcher
Indicates that one entity corresponds to, aligns with, or is considered an appropriate or equivalent counterpart to another entity based on specified criteria.
-
C.
relatedAlgorithm
chosen
Indicates that one algorithm has a meaningful connection or association with another algorithm, such as similarity, dependency, or complementary function.
-
D.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
E.
matchResult
Indicates the outcome or final status produced by a particular match or game between participants.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:58 p.m.