Triple
T8650315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai New International Expo Centre |
E205082
|
entity |
| Predicate | hasTotalIndoorExhibitionSpace |
P9481
|
FINISHED |
| Object | over 200000 square metres |
—
|
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: over 200000 square metres | Statement: [Shanghai New International Expo Centre, hasTotalIndoorExhibitionSpace, over 200000 square metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTotalIndoorExhibitionSpace Context triple: [Shanghai New International Expo Centre, hasTotalIndoorExhibitionSpace, over 200000 square metres]
-
A.
hasIndoorExhibits
Indicates that an entity provides or contains exhibits that are located indoors.
-
B.
hasExhibitionArea
chosen
Indicates that an entity includes or provides a designated space or area for exhibitions or displays.
-
C.
exhibitionSpaceType
Indicates the specific kind or category of space used to display or present exhibitions.
-
D.
hasIndoorArea
Indicates that an entity possesses or includes an area or space that is located indoors or within a building.
-
E.
hasOutdoorExhibits
Indicates that a place or institution includes exhibits or displays located in outdoor or open-air areas.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4813d0548190b203e594acc38c8f |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.