Triple
T36260867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die Wucht XXIII |
E892079
|
entity |
| Predicate | associatedWithArtistBirthPlace |
P58095
|
FINISHED |
| Object | Leipzig |
E38199
|
NE 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: Leipzig | Statement: [Die Wucht XXIII, associatedWithArtistBirthPlace, Leipzig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithArtistBirthPlace Context triple: [Die Wucht XXIII, associatedWithArtistBirthPlace, Leipzig]
-
A.
musicArtistOriginCity
Indicates the city from which a music artist originates or is primarily associated.
-
B.
hasPerformerBirthCity
Indicates the city in which the performer was born.
-
C.
isBirthplaceRelatedTo
chosen
Indicates that there is a relationship between an entity and a birthplace, such as being born there or otherwise closely associated with that place of birth.
-
D.
subjectLocationRelationToArtist
Indicates the spatial or locational relationship between a subject and an artist (e.g., where the subject is positioned relative to the artist).
-
E.
nearBirthplaceOf
Indicates that one entity is located close to the place where another entity was born.
- F. None of above.
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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a397d64825481909323a3599f552dd4 |
completed | June 22, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.