Triple
T1975795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SETSqx |
E42907
|
entity |
| Predicate | priceDiscoveryMethod |
P7311
|
FINISHED |
| Object | auction uncrossing prices |
—
|
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: auction uncrossing prices | Statement: [SETSqx, priceDiscoveryMethod, auction uncrossing prices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priceDiscoveryMethod Context triple: [SETSqx, priceDiscoveryMethod, auction uncrossing prices]
-
A.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
B.
priceReference
Indicates a relationship where one price is used as a benchmark or basis for determining, comparing, or deriving another price.
-
C.
discoveryMethod
chosen
Indicates the process, technique, or approach by which something was found, detected, or identified.
-
D.
pricingStrategy
Indicates the approach or method used to set, adjust, or structure prices for products or services in a given context.
-
E.
launchPriceDescription
Indicates the descriptive text explaining the initial price at which a product or service is first launched or offered.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f835108190b0709ccf3a487a96 |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff9a09c8190a81fa13f4b85bc79 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.