Triple
T1653356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Stock Exchange |
E35742
|
entity |
| Predicate | openingAuctionMethod |
P9833
|
FINISHED |
| Object | call auction |
—
|
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: call auction | Statement: [Tokyo Stock Exchange, openingAuctionMethod, call auction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingAuctionMethod Context triple: [Tokyo Stock Exchange, openingAuctionMethod, call auction]
-
A.
openingAuction
chosen
Indicates that an entity participates in, is associated with, or is defined in the context of an opening auction event or process.
-
B.
closingAuction
Indicates that an auction is in its final phase where bidding is concluding and the final price is being determined.
-
C.
automaticBidBasis
Indicates that one entity’s bid amount is determined automatically based on a specified rule, condition, or reference value relative to another entity.
-
D.
closingAuctionTimeLocal
Indicates the local-time moment at which an auction or bidding process is scheduled to end.
-
E.
grantsAutomaticBidTo
Indicates that one entity confers an automatic qualification or guaranteed entry (typically to a competition or event) upon another entity.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.