Triple
T2137446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Rugby World Cup |
E46686
|
entity |
| Predicate | hostSelectionProcess |
P126
|
FINISHED |
| Object | IRB Council vote |
—
|
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: IRB Council vote | Statement: [2011 Rugby World Cup, hostSelectionProcess, IRB Council vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSelectionProcess Context triple: [2011 Rugby World Cup, hostSelectionProcess, IRB Council vote]
-
A.
hostSelection
Indicates the choice or designation of a particular host from a set of possible hosts for a given purpose or interaction.
-
B.
holderSelection
Indicates that a particular entity has been chosen or designated to serve as the holder of another entity or resource.
-
C.
selectionProcess
chosen
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
-
D.
hostCitySelectionMethod
Indicates the process or criteria by which a host city is chosen for an event or activity.
-
E.
boardingProcess
Indicates the process or sequence of actions by which passengers move from a waiting area onto a vehicle (such as an airplane, train, or bus).
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.