Triple
T28818852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brand-Erbisdorf |
E727703
|
entity |
| Predicate | hasMunicipalStatusInGermany |
P37705
|
FINISHED |
| Object | Stadt |
—
|
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: Stadt | Statement: [Brand-Erbisdorf, hasMunicipalStatusInGermany, Stadt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalStatusInGermany Context triple: [Brand-Erbisdorf, hasMunicipalStatusInGermany, Stadt]
-
A.
hasMunicipalAreaRankingInGermany
Indicates that a municipality holds a specific rank or position in comparison to other municipalities in Germany based on its area size.
-
B.
isMunicipalStatus
chosen
Indicates that an entity possesses a specific legally defined municipal status or classification within a governmental or administrative system.
-
C.
isBavarianMunicipality
Indicates that an entity functions as a municipality located within the federal state of Bavaria.
-
D.
hasMunicipalStatusUntil
Indicates that an entity possessed municipal status up to, but not beyond, a specified point in time.
-
E.
usedToHaveMunicipalStatus
Indicates that an entity previously held municipal status (was officially recognized as a municipality) but no longer does.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 6:33 a.m.