Triple
T21391750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otoya Yamaguchi |
E527669
|
entity |
| Predicate | wroteSlogan |
P13882
|
FINISHED |
| Object | Long live the Emperor |
—
|
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: Long live the Emperor | Statement: [Otoya Yamaguchi, wroteSlogan, Long live the Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteSlogan Context triple: [Otoya Yamaguchi, wroteSlogan, Long live the Emperor]
-
A.
sloganGivenBy
chosen
Indicates that a particular slogan is provided, coined, or assigned by a specific entity.
-
B.
sloganForm
Indicates that one entity serves as the slogan or advertising catchphrase associated with another entity.
-
C.
sloganInspired
Indicates that one slogan was created, influenced, or shaped by ideas, style, or content drawn from another source.
-
D.
sloganConcept
Indicates that a particular concept, idea, or theme is expressed or represented by a given slogan.
-
E.
sloganUsedIn
Indicates that a particular slogan is employed or featured within a specific context, such as a campaign, advertisement, or organization.
- 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee62cbfef08190a33ac1f198c82cd0 |
completed | April 26, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:13 p.m.