Triple
T26864421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemeindeordnung Baden-Württemberg |
E676423
|
entity |
| Predicate | adressiert |
P126591
|
FINISHED |
| Object | Gemeindeverwaltungen |
—
|
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: Gemeindeverwaltungen | Statement: [Gemeindeordnung Baden-Württemberg, adressiert, Gemeindeverwaltungen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adressiert Context triple: [Gemeindeordnung Baden-Württemberg, adressiert, Gemeindeverwaltungen]
-
A.
addressing
Indicates that one entity is directing speech, communication, or attention specifically toward another entity.
-
B.
addressedFor
chosen
Indicates that something is directed, designated, or intended for a particular recipient or target.
-
C.
addressedBy
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
D.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
-
E.
addresseeOf
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 5:27 a.m.