Triple
T21560803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tried in the Furnace |
E532017
|
entity |
| Predicate | hasMainTone |
P53965
|
FINISHED |
| Object | humorous |
—
|
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: humorous | Statement: [Tried in the Furnace, hasMainTone, humorous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainTone Context triple: [Tried in the Furnace, hasMainTone, humorous]
-
A.
hasMainGenre
Indicates that an entity’s primary or most characteristic genre is the specified genre.
-
B.
hasTonalityShift
Indicates a change in the tonal quality, mood, or key within a piece or segment, marking a shift from one tonality to another.
-
C.
hasEndingTone
chosen
Indicates that something concludes with a particular tone, mood, or intonational quality.
-
D.
hasMainSpeaker
Indicates that one entity serves as the primary or principal speaker associated with another entity, such as an event, recording, or presentation.
-
E.
hasLiturgicalTone
Indicates that something (such as a chant, text, or musical phrase) is associated with or performed in a specific liturgical tone or mode.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e2db2c81908b965312c50d4354 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.