Triple
T1975783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SETSqx |
E42907
|
entity |
| Predicate | auctionFrequency |
P32990
|
FINISHED |
| Object | periodic auctions at scheduled intervals |
—
|
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: periodic auctions at scheduled intervals | Statement: [SETSqx, auctionFrequency, periodic auctions at scheduled intervals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: auctionFrequency Context triple: [SETSqx, auctionFrequency, periodic auctions at scheduled intervals]
-
A.
auctionRecord
Indicates that there exists a documented record of an auction event involving the related entities.
-
B.
openingAuction
Indicates that an entity participates in, is associated with, or is defined in the context of an opening auction event or process.
-
C.
closingAuction
Indicates that an auction is in its final phase where bidding is concluding and the final price is being determined.
-
D.
awardedFrequency
Indicates how often an award or recognition is given within a specified time period.
-
E.
automaticBidBasis
Indicates that one entity’s bid amount is determined automatically based on a specified rule, condition, or reference value relative to another 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_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. |
| PDg | Predicate description generation | batch_69abb09b27e88190bff164040fef6d7e |
completed | March 7, 2026, 4:59 a.m. |
Created at: March 4, 2026, 7:36 p.m.