Triple
T29576147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphonische Dichtung in zwei Teilen |
E753447
|
entity |
| Predicate | conception |
P178311
|
FINISHED |
| Object | two-part symphonic poem |
—
|
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: two-part symphonic poem | Statement: [Symphonische Dichtung in zwei Teilen, conception, two-part symphonic poem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conception Context triple: [Symphonische Dichtung in zwei Teilen, conception, two-part symphonic poem]
-
A.
conceptionBy
Indicates that one entity is conceived or brought into existence by another entity.
-
B.
conceivedWhile
Indicates that one entity was conceived during the time period in which another specified condition, event, or circumstance was occurring.
-
C.
conceptionPeriod
Indicates the time interval during which a conception or initial formation of something occurs.
-
D.
conceptionDescribedAs
Indicates that a conception or idea is characterized, defined, or portrayed in a particular way.
-
E.
conceptionLocation
Indicates the place where the act or event of conception of an individual occurred.
- F. None of above. chosen
Provenance (4 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 28, 2026, 6:03 p.m.