Triple
T6003937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2026 FIFA World Cup |
E133661
|
entity |
| Predicate | biddingRival |
P68648
|
FINISHED |
| Object | Morocco 2026 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: Morocco 2026 bid | Statement: [2026 FIFA World Cup, biddingRival, Morocco 2026 bid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biddingRival Context triple: [2026 FIFA World Cup, biddingRival, Morocco 2026 bid]
-
A.
biddingRivalCountry
Indicates a relationship where one country competes with another in placing bids, typically for the same contract, project, or opportunity.
-
B.
bidRivalCity
Indicates a competitive bidding relationship where one city submits an offer in direct rivalry to another city.
-
C.
bidWinner
Indicates that the referenced entity is the winner of a particular bidding or auction process.
-
D.
bidsFrom
Indicates that one entity has submitted or placed a bid originating from it toward another entity or item.
-
E.
biddingCity
Indicates the city in which a bidding or auction-related activity takes place or is registered.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f0f63148190826198281dce3713 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8c5bfc8190b986a7071d1b23e3 |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:06 p.m.