Triple
T23042741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2030 FIFA World Cup |
E573782
|
entity |
| Predicate | coHostingFormat |
P150764
|
FINISHED |
| Object | multi-national hosting |
—
|
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: multi-national hosting | Statement: [2030 FIFA World Cup, coHostingFormat, multi-national hosting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coHostingFormat Context triple: [2030 FIFA World Cup, coHostingFormat, multi-national hosting]
-
A.
coHostingPlan
Indicates a planned arrangement in which two or more parties jointly host or organize an event or activity.
-
B.
hostedFormat
Indicates that an entity is provided or made available in a particular hosted format or presentation style.
-
C.
hostingLocation
Indicates the place or venue where an event, activity, or entity is being hosted or takes place.
-
D.
hostedOn
Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
-
E.
supportsHosting
Indicates that one entity provides the necessary resources or capabilities for another entity to host or run something (such as an application, service, or content).
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18516417081908bf747b20de23a75 |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:54 p.m.