Triple
T34351637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wörth an der Isar |
E881594
|
entity |
| Predicate | isInBavarianAdministrativeRegion |
P174787
|
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: [Wörth an der Isar, isInBavarianAdministrativeRegion, Niederbayern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInBavarianAdministrativeRegion Context triple: [Wörth an der Isar, isInBavarianAdministrativeRegion, Niederbayern]
-
A.
isBavarianMunicipality
Indicates that an entity functions as a municipality located within the federal state of Bavaria.
-
B.
isInBundesland
chosen
Indicates that one entity (typically a place or city) is located within a specific German federal state (Bundesland).
-
C.
isLocatedInFranconiaRegion
Indicates that something is situated within the geographical boundaries of the Franconia region.
-
D.
federalStateOfGermany
Indicates that one entity is a federal state (Bundesland) that is a constituent state within the country of Germany.
-
E.
containsGermanSpeakingArea
Indicates that one entity geographically includes an area where German is predominantly spoken.
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.