Triple
T11440800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo 2008 site |
E271137
|
entity |
| Predicate | themeOfHostedEvent |
P25955
|
FINISHED |
| Object | Water and Sustainable Development |
—
|
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: Water and Sustainable Development | Statement: [Expo 2008 site, themeOfHostedEvent, Water and Sustainable Development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeOfHostedEvent Context triple: [Expo 2008 site, themeOfHostedEvent, Water and Sustainable Development]
-
A.
hostsEvent
Indicates that an entity organizes and provides the venue or setting for an event to take place.
-
B.
themeFor
chosen
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
C.
themedAs
Indicates that something is characterized, styled, or organized according to a particular theme or motif.
-
D.
campaignTheme
Indicates the central idea or message that characterizes and unifies a particular campaign.
-
E.
hostsTypeOfEvent
Indicates that an entity organizes or provides the venue for a particular type or category of event.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d80888190c8190b6365550ffe4931c |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.