Triple
T14849399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neubebauung des Augustusplatzes in Leipzig |
E349186
|
entity |
| Predicate | funktionalesZiel |
P64674
|
FINISHED |
| Object | Stärkung von Bildung und Kultur im Stadtzentrum |
—
|
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ärkung von Bildung und Kultur im Stadtzentrum | Statement: [Neubebauung des Augustusplatzes in Leipzig, funktionalesZiel, Stärkung von Bildung und Kultur im Stadtzentrum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: funktionalesZiel Context triple: [Neubebauung des Augustusplatzes in Leipzig, funktionalesZiel, Stärkung von Bildung und Kultur im Stadtzentrum]
-
A.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
B.
outcomeFocus
Indicates that the primary emphasis or attention is placed on the results or consequences of an action or process.
-
C.
기능
Indicates that an entity has a particular function, role, or operational capability.
-
D.
intendedFunction
Indicates that something is designed or purposed to perform a particular role, use, or function.
-
E.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
- 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.