Triple
T2568855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einigungsvertrag |
E57615
|
entity |
| Predicate | wirktSichAusAuf |
P25489
|
FINISHED |
| Object | politisches System Deutschlands |
—
|
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: politisches System Deutschlands | Statement: [Einigungsvertrag, wirktSichAusAuf, politisches System Deutschlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wirktSichAusAuf Context triple: [Einigungsvertrag, wirktSichAusAuf, politisches System Deutschlands]
-
A.
areAffectedBy
chosen
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
B.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
C.
affectsVariant
Indicates that one entity has an influence or impact on a specific variant or version of another entity.
-
D.
hasSubstrateInfluenceOn
Indicates that one substrate affects, modifies, or determines the behavior, activity, or properties of another entity or process.
-
E.
hasUpstreamImpactOn
Indicates that one entity’s actions, changes, or outputs affect another entity that is positioned earlier in a process, flow, or dependency chain.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd380d6e081909c124e8a0b7feef3 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.