Triple
T27967549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bauministerium |
E704765
|
entity |
| Predicate | hatKompetenzbereich |
P18508
|
FINISHED |
| Object | Baupolitik |
—
|
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: Baupolitik | Statement: [Bauministerium, hatKompetenzbereich, Baupolitik]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatKompetenzbereich Context triple: [Bauministerium, hatKompetenzbereich, Baupolitik]
-
A.
competenceArea
chosen
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
-
B.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
-
C.
concurrentCompetenceArea
Indicates that two or more competence areas are active or applicable at the same time in relation to the same context, task, or entity.
-
D.
skillSet
Indicates that an entity possesses or is associated with a particular collection of skills or competencies.
-
E.
hasCompetence
Indicates that an entity possesses the ability, skill, or qualification to perform a specific task or function effectively.
- 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.