Triple
T23310484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nun danket alle Gott |
E590568
|
entity |
| Predicate | originalMeter |
P142894
|
FINISHED |
| Object | 6.7.6.7.6.6.6.6 |
—
|
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: 6.7.6.7.6.6.6.6 | Statement: [Nun danket alle Gott, originalMeter, 6.7.6.7.6.6.6.6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalMeter Context triple: [Nun danket alle Gott, originalMeter, 6.7.6.7.6.6.6.6]
-
A.
meter
Indicates a measurement relationship where one entity quantifies the length, distance, or extent of another in meters.
-
B.
hasMeter
Indicates that one entity possesses, uses, or is associated with a specific meter (a measuring device or metrical pattern).
-
C.
meterForm
chosen
Indicates that one entity is the specific metrical pattern or verse form in which another entity (such as a poem or song) is composed.
-
D.
meterSystem
Indicates that one entity uses, is measured in, or is associated with a particular system of meters or measurement units.
-
E.
originalWorkMeter
Indicates that a work’s measurement or metrical structure is derived from or corresponds to that of an original source work.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972acad08190bb56541b822555cd |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:05 p.m.