Triple
T2470412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Battle Hymn of the Republic |
E55358
|
entity |
| Predicate | chorusIncludesWord |
P24842
|
FINISHED |
| Object | hallelujah |
—
|
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: hallelujah | Statement: [The Battle Hymn of the Republic, chorusIncludesWord, hallelujah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chorusIncludesWord Context triple: [The Battle Hymn of the Republic, chorusIncludesWord, hallelujah]
-
A.
hasChorusBy
Indicates that something (typically a musical work or song) includes a chorus section that is performed, written, or provided by a specified entity.
-
B.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
C.
includesSaying
chosen
Indicates that one entity (such as a text, speech, or communication) contains or incorporates a particular saying, phrase, or quoted expression.
-
D.
hasChoir
Indicates that an entity possesses, maintains, or is associated with a choir.
-
E.
includesClause
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
- 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_69ab49e3622c8190ad22afa2c4fbb807 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0b3ea308190a6d8499c2a542c50 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.