Triple
T16482695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo 2002 |
E400360
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Expo.02 |
E400360
|
NE 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: Expo.02 | Statement: [Expo 2002, alsoKnownAs, Expo.02]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Expo.02 Context triple: [Expo 2002, alsoKnownAs, Expo.02]
-
A.
Expo 2002
chosen
Expo 2002 was the sixth Swiss national exposition, a large-scale cultural and technological showcase held in 2002 across several sites in the country.
-
B.
Expo 83
Expo 83 was a specialized international exposition held in Plovdiv, Bulgaria in 1983, showcasing technological, industrial, and cultural achievements.
-
C.
Expo 85
Expo 85 was a world's fair held in Tsukuba, Japan, showcasing advances in science and technology during the mid-1980s.
-
D.
Expo '81
Expo '81 was a world's fair held in 1981, serving as the subsequent international exposition after Expo '75.
-
E.
Expo
Expo is an open-source platform and toolchain for building, deploying, and iterating on React Native applications.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e03643881908b16ddb9004af5d0 |
completed | April 18, 2026, 7:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a005820790c819088d953eeea09328d |
completed | May 10, 2026, 10:04 a.m. |
Created at: April 10, 2026, 5:13 a.m.