Triple
T28710514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Heard the Bells on Christmas Day |
E729817
|
entity |
| Predicate | sourcePoemMeter |
P30317
|
FINISHED |
| Object | common hymn meter |
—
|
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: common hymn meter | Statement: [I Heard the Bells on Christmas Day, sourcePoemMeter, common hymn meter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourcePoemMeter Context triple: [I Heard the Bells on Christmas Day, sourcePoemMeter, common hymn meter]
-
A.
poemLength
Indicates the length or extent of a poem, typically measured in units such as lines, verses, or words.
-
B.
rhymeScheme
Indicates the pattern of end sounds in a sequence of lines, showing which lines rhyme with each other.
-
C.
poeticStructure
chosen
Indicates a relationship where one entity defines, embodies, or specifies the formal poetic organization (such as meter, rhyme scheme, or stanza pattern) used by another entity.
-
D.
typicalFootCountPerHemistich
Indicates the usual number of metrical feet found in each hemistich (half-line) of a verse.
-
E.
numberOfStanzasInOriginalPoem
Indicates the total count of stanzas contained in the poem’s original version.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 5:47 a.m.