Triple
T8650336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai New International Expo Centre |
E205082
|
entity |
| Predicate | hasWebsiteLanguage |
P16555
|
FINISHED |
| Object | Chinese |
—
|
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: Chinese | Statement: [Shanghai New International Expo Centre, hasWebsiteLanguage, Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWebsiteLanguage Context triple: [Shanghai New International Expo Centre, hasWebsiteLanguage, Chinese]
-
A.
languageOfOfficialWebsite
chosen
Indicates the language in which an entity’s official website is primarily written or presented.
-
B.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
C.
hasLanguages
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
D.
hasPrimaryLanguage1
Indicates that an entity’s main or most commonly used language is the specified language.
-
E.
isWorldLanguage
Indicates that a language is widely used across multiple countries or regions and serves as a common means of communication beyond its original native community.
- 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.