Triple
T31394794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutheran chorale tradition |
E800835
|
entity |
| Predicate | centralGenre |
P47442
|
FINISHED |
| Object | congregational hymn |
—
|
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: congregational hymn | Statement: [Lutheran chorale tradition, centralGenre, congregational hymn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralGenre Context triple: [Lutheran chorale tradition, centralGenre, congregational hymn]
-
A.
commonGenre
Indicates that two entities share at least one genre in common.
-
B.
genreWithin
chosen
Indicates that one genre is a subgenre or more specific category contained within another, broader genre.
-
C.
secondaryGenre
Indicates that an entity (such as a work or item) has an additional, non-primary genre classification associated with it.
-
D.
genre
Indicates the artistic or thematic category to which a work (such as a book, film, or song) belongs.
-
E.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 29, 2026, 9:19 p.m.