Triple
T29035091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eichendorff-Lieder |
E737835
|
entity |
| Predicate | usesTextForm |
P26269
|
FINISHED |
| Object | German lyric poetry |
—
|
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: German lyric poetry | Statement: [Eichendorff-Lieder, usesTextForm, German lyric poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTextForm Context triple: [Eichendorff-Lieder, usesTextForm, German lyric poetry]
-
A.
useText
Indicates that one entity employs or applies a specific text as a resource, tool, or content in performing an action or fulfilling a function.
-
B.
usesTextService
Indicates that an entity makes use of a text-based service to perform some function or obtain some benefit.
-
C.
usesTextBy
Indicates that one entity makes use of or relies on a text authored or provided by another entity.
-
D.
usesForm
chosen
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
-
E.
allowsText
Indicates that one entity permits or supports the use, input, or display of textual content in relation to another entity.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.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 28, 2026, 9:57 a.m.