Triple
T26079981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 FIFA World Cup matches |
E657807
|
entity |
| Predicate | hostCityIncluded |
P128457
|
FINISHED |
| Object | Port Elizabeth |
—
|
NE NERFINISHED |
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: Port Elizabeth | Statement: [2010 FIFA World Cup matches, hostCityIncluded, Port Elizabeth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCityIncluded Context triple: [2010 FIFA World Cup matches, hostCityIncluded, Port Elizabeth]
-
A.
hostCitiesInclude
chosen
Indicates that a particular set, event, or organization has among its host locations the specified city or cities.
-
B.
hostCityFeature
Indicates that a particular feature, attribute, or characteristic is associated with or present in a host city.
-
C.
hostCityInstanceOf
Indicates that a specific host city is an instance of a particular class or type of host city (e.g., Olympic host city, World Cup host city).
-
D.
hostCityOfEvent
Indicates that a city serves as the location where a particular event is held or takes place.
-
E.
hostCitySelection
Indicates the selection of a particular city to serve as the official host location for an event or activity.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 7:37 p.m.