Triple
T14849387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neubebauung des Augustusplatzes in Leipzig |
E349186
|
entity |
| Predicate | hatAspekt |
P61123
|
FINISHED |
| Object | städtebauliche Neuordnung |
—
|
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: städtebauliche Neuordnung | Statement: [Neubebauung des Augustusplatzes in Leipzig, hatAspekt, städtebauliche Neuordnung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatAspekt Context triple: [Neubebauung des Augustusplatzes in Leipzig, hatAspekt, städtebauliche Neuordnung]
-
A.
hatTeil
Indicates that something is a part or component of something else.
-
B.
hatOrigin
Indicates the place or source from which a hat was originally produced or came.
-
C.
hatPattern
Indicates that one entity has a hat characterized by a specific pattern or design.
-
D.
aspect
Indicates a specific temporal phase or manner in which an action, event, or state unfolds or is viewed (e.g., ongoing, completed, habitual).
-
E.
coversAspect
chosen
Indicates that one entity addresses, includes, or deals with a particular aspect or facet of another entity or topic.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded43eee188190bf24dc475b3abe28 |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:53 a.m.