Triple
T27967568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bauministerium |
E704765
|
entity |
| Predicate | verfügtÜber |
P13854
|
FINISHED |
| Object | Fachabteilungen für Bauwesen |
—
|
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: Fachabteilungen für Bauwesen | Statement: [Bauministerium, verfügtÜber, Fachabteilungen für Bauwesen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verfügtÜber Context triple: [Bauministerium, verfügtÜber, Fachabteilungen für Bauwesen]
-
A.
has
chosen
Indicates that one entity possesses, owns, contains, or includes another entity as part of its state or composition.
-
B.
availableWith
Indicates that one entity can be obtained, accessed, or used in conjunction with another entity.
-
C.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
D.
holdsFor
Indicates that a particular relationship or condition remains true over a specified interval or duration of time.
-
E.
holdsOver
Indicates that a certain condition, state, or relationship remains valid or continues to apply across a specified period, context, or range.
- 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_69ef841061e48190b5570f9562f7434d |
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:36 p.m.