Triple
T7577485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hunchback of Notre Dame (stage musical) |
E179394
|
entity |
| Predicate | includesThemes |
P6142
|
FINISHED |
| Object | religion |
—
|
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: religion | Statement: [The Hunchback of Notre Dame (stage musical), includesThemes, religion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesThemes Context triple: [The Hunchback of Notre Dame (stage musical), includesThemes, religion]
-
A.
containsThemeArea
chosen
Indicates that one entity includes or encompasses a specific thematic area as part of its scope or content.
-
B.
followsInTheme
Indicates that one element continues or succeeds another while maintaining the same theme or thematic context.
-
C.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
D.
supportsThemeOf
Indicates that one entity reinforces, aligns with, or contributes to the central theme expressed by another entity.
-
E.
themeExamples
Indicates that the related entity serves as an example or illustration of the theme expressed by the subject.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f94cdbec81909f2ba7ce04e49931 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.