Triple
T10319042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo 2017 sphere (Nur Alem) |
E242092
|
entity |
| Predicate | themeExhibited |
P5290
|
FINISHED |
| Object | Future Energy |
—
|
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: Future Energy | Statement: [Expo 2017 sphere (Nur Alem), themeExhibited, Future Energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeExhibited Context triple: [Expo 2017 sphere (Nur Alem), themeExhibited, Future Energy]
-
A.
exhibitTheme
chosen
Indicates that something (such as a work, event, or presentation) presents, embodies, or is organized around a particular theme.
-
B.
exhibitionType
Indicates the specific category or kind of exhibition associated with an entity (e.g., art show, trade fair, scientific exhibit).
-
C.
exhibition
Indicates that an entity is organizing, hosting, or serving as a public display or presentation of another entity (such as artworks, objects, or information).
-
D.
exhibitedAs
Indicates that something is presented or displayed in a particular context, such as in a show, gallery, or exhibition.
-
E.
exhibitionUse
Indicates that something is used, intended, or designated for display in an exhibition or exhibit context.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:49 a.m.