Triple
T36912172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geh aus, mein Herz, und suche Freud |
E912937
|
entity |
| Predicate | approximateYearOfText |
P187456
|
FINISHED |
| Object | 1653 |
—
|
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: 1653 | Statement: [Geh aus, mein Herz, und suche Freud, approximateYearOfText, 1653]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateYearOfText Context triple: [Geh aus, mein Herz, und suche Freud, approximateYearOfText, 1653]
-
A.
approximateYearWritten
Indicates the estimated calendar year in which something was written, when the exact year is not known.
-
B.
textPublicationApproxYear
chosen
Indicates that a text was published around a specified year, with the year representing an approximate rather than exact publication date.
-
C.
retitleApproxYear
Indicates that an entity was retitled or renamed around an approximate year, rather than at a precisely known date.
-
D.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
E.
releaseApproximateYear
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: May 3, 2026, 4:13 p.m.