Triple
T29853549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Der Jäger |
E758125
|
entity |
| Predicate | cycleNumbering |
P168579
|
FINISHED |
| Object | No. 14 in Die schöne Müllerin |
—
|
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: No. 14 in Die schöne Müllerin | Statement: [Der Jäger, cycleNumbering, No. 14 in Die schöne Müllerin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cycleNumbering Context triple: [Der Jäger, cycleNumbering, No. 14 in Die schöne Müllerin]
-
A.
chronNumber
chosen
Indicates that one entity is assigned a specific chronological number or position in an ordered sequence relative to others.
-
B.
cycleType
Indicates the specific kind or category of cycle involved in a repeated or cyclical process or relationship.
-
C.
cycleWith
Indicates that two or more entities participate together in a cycling activity, such as riding bicycles along the same route or at the same time.
-
D.
cycleConsistsOf
Indicates that a cycle is composed of, or made up from, the specified component elements or segments.
-
E.
catalogueNumberOfCycle
Indicates that an entity is assigned a specific catalogue number identifying a particular cycle within a cataloging system.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 29, 2026, 5:45 p.m.