Triple
T27967561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bauministerium |
E704765
|
entity |
| Predicate | hatOrganisationsform |
P3580
|
FINISHED |
| Object | oberste Bundes- oder Landesbehörde |
—
|
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: oberste Bundes- oder Landesbehörde | Statement: [Bauministerium, hatOrganisationsform, oberste Bundes- oder Landesbehörde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatOrganisationsform Context triple: [Bauministerium, hatOrganisationsform, oberste Bundes- oder Landesbehörde]
-
A.
modeOfOrganization
Indicates the way in which an entity, group, or activity is structured, arranged, or organized.
-
B.
organizationType
chosen
Indicates the specific category or classification of an organization in terms of its nature, structure, or primary function.
-
C.
formsOrganization
Indicates that an entity initiates or creates a new organization or formal group.
-
D.
hostsOrganizationType
Indicates that an entity serves as the hosting venue or platform for organizations of a specified type.
-
E.
organType
Indicates that one entity is classified as a specific type or category of organ in relation to 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b323ea48190917e104d4d5fb1bf |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:36 p.m.