Triple
T26864385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemeindeordnung Baden-Württemberg |
E676423
|
entity |
| Predicate | giltIn |
P120649
|
FINISHED |
| Object | Land Baden-Württemberg |
—
|
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: Land Baden-Württemberg | Statement: [Gemeindeordnung Baden-Württemberg, giltIn, Land Baden-Württemberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: giltIn Context triple: [Gemeindeordnung Baden-Württemberg, giltIn, Land Baden-Württemberg]
-
A.
geldtIn
chosen
Indicates that a rule, condition, or state is applicable or in effect within a specific context, scope, or domain.
-
B.
gulType
Indicates the specific kind or category of a gul (as defined in the given context) that an entity belongs to.
-
C.
givenFor
Indicates that something is provided, offered, or assigned in favor of or on behalf of a particular entity or purpose.
-
D.
inlaidWith
Indicates that one object has decorative material set into its surface, typically flush with it, using a contrasting substance or pattern.
-
E.
holdsIn
Indicates that a relationship, condition, or event is valid or occurs within a specified time interval or temporal context.
- 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_69f61e96d45881909f2b93dfc522064f |
completed | May 2, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:27 a.m.