Triple
T8020741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSE |
E186733
|
entity |
| Predicate | openingAuctionTime |
P80603
|
FINISHED |
| Object | 09:00 JST |
—
|
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: 09:00 JST | Statement: [TSE, openingAuctionTime, 09:00 JST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingAuctionTime Context triple: [TSE, openingAuctionTime, 09:00 JST]
-
A.
openingAuction
Indicates that an entity participates in, is associated with, or is defined in the context of an opening auction event or process.
-
B.
closingAuctionTimeLocal
Indicates the local-time moment at which an auction or bidding process is scheduled to end.
-
C.
closingAuction
Indicates that an auction is in its final phase where bidding is concluding and the final price is being determined.
-
D.
auctionMethod
Indicates the type or procedure of auction used to conduct a sale or bidding process between parties.
-
E.
auctionRecord
Indicates that there exists a documented record of an auction event involving the related entities.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8d90488190b57d1e748e272061 |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:20 p.m.