Triple
T27957414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landesminister |
E703588
|
entity |
| Predicate | istGebundenAn |
P158832
|
FINISHED |
| Object | Grundgesetz der Bundesrepublik Deutschland |
—
|
NE NERFINISHED |
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: Grundgesetz der Bundesrepublik Deutschland | Statement: [Landesminister, istGebundenAn, Grundgesetz der Bundesrepublik Deutschland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: istGebundenAn Context triple: [Landesminister, istGebundenAn, Grundgesetz der Bundesrepublik Deutschland]
-
A.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
B.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
C.
boundIs
chosen
Indicates that one entity is constrained, limited, or obligated by another entity, condition, or rule.
-
D.
oftenBoundIn
Indicates that one entity is frequently enclosed, packaged, or contained within another entity.
-
E.
annexedBy
Indicates that one entity has been incorporated into and brought under the control or sovereignty of another entity.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:29 p.m.