Triple
T34366296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-I-C-K-E-Y M-O-U-S-E |
E882020
|
entity |
| Predicate | isChantedAs |
P175621
|
FINISHED |
| Object | character name cheer |
—
|
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: character name cheer | Statement: [M-I-C-K-E-Y M-O-U-S-E, isChantedAs, character name cheer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isChantedAs Context triple: [M-I-C-K-E-Y M-O-U-S-E, isChantedAs, character name cheer]
-
A.
alsoChantedIn
Indicates that a chant, hymn, or recitation is performed or used in an additional context, location, or tradition beyond its primary one.
-
B.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
-
C.
usedAsChant
chosen
Indicates that something (typically a phrase, text, or sound) is employed as a chant in a ritual, performance, or repetitive vocal practice.
-
D.
hasChantingStyle
Indicates that an entity is associated with or characterized by a particular style or manner of chanting.
-
E.
languageOfChant
Indicates the language in which a chant is performed or expressed.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:58 a.m.