Triple
T7548929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2026 Commonwealth Games |
E178477
|
entity |
| Predicate | originalBidType |
P77934
|
FINISHED |
| Object | state-wide regional bid |
—
|
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: state-wide regional bid | Statement: [2026 Commonwealth Games, originalBidType, state-wide regional bid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBidType Context triple: [2026 Commonwealth Games, originalBidType, state-wide regional bid]
-
A.
biddingProcessType
Indicates the specific method or procedure used to conduct a bidding or tendering process between parties.
-
B.
automaticBidBasis
Indicates that one entity’s bid amount is determined automatically based on a specified rule, condition, or reference value relative to another entity.
-
C.
bidsFrom
Indicates that one entity has submitted or placed a bid originating from it toward another entity or item.
-
D.
originalType
Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
-
E.
bidWinner
Indicates that the referenced entity is the winner of a particular bidding or auction process.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f89b9afc8190b3e61a8e2cea7ad7 |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:49 p.m.