Triple
T38598736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World in Motion – World in Touch |
E934152
|
entity |
| Predicate | isOfficialThemeSloganOf |
P132650
|
FINISHED |
| Object | Expo 86 |
—
|
NE NERFINISHED |
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 86 | Statement: [World in Motion – World in Touch, isOfficialThemeSloganOf, Expo 86]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOfficialThemeSloganOf Context triple: [World in Motion – World in Touch, isOfficialThemeSloganOf, Expo 86]
-
A.
sloganUsedBy
Indicates that a particular slogan is employed or adopted by a specific entity (such as a person, organization, or brand) in its communication or branding.
-
B.
hasSloganOrKeyPhrase
chosen
Indicates that an entity is associated with a specific slogan, tagline, or key phrase used to represent or promote it.
-
C.
sloganGivenBy
Indicates that a particular slogan is provided, coined, or assigned by a specific entity.
-
D.
sloganUsedIn
Indicates that a particular slogan is employed or featured within a specific context, such as a campaign, advertisement, or organization.
-
E.
hasSloganType
Indicates the specific category or type of slogan associated with an entity.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.