Triple
T31564530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruckberg (Landshut district) |
E805368
|
entity |
| Predicate | isInRegionalDivision |
P52313
|
FINISHED |
| Object | Niederbayern |
—
|
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: Niederbayern | Statement: [Bruckberg (Landshut district), isInRegionalDivision, Niederbayern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInRegionalDivision Context triple: [Bruckberg (Landshut district), isInRegionalDivision, Niederbayern]
-
A.
isRegional
Indicates that something pertains to, is characteristic of, or is limited to a specific geographic region or area.
-
B.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
C.
isInSubregion
Indicates that one region or area is located within the boundaries of another, more specific subregion.
-
D.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
-
E.
isPartOfDivision
chosen
Indicates that one entity belongs to, or is contained within, a specific division of a larger organizational or structural unit.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:16 p.m.