Triple
T25737423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waidhofen an der Thaya |
E645411
|
entity |
| Predicate | hasCadastralMunicipality |
P128277
|
FINISHED |
| Object | Altwaidhofen |
—
|
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: Altwaidhofen | Statement: [Waidhofen an der Thaya, hasCadastralMunicipality, Altwaidhofen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCadastralMunicipality Context triple: [Waidhofen an der Thaya, hasCadastralMunicipality, Altwaidhofen]
-
A.
hasCadastralCommunity
chosen
Indicates a relationship where an entity is associated with, or located within, a specific cadastral community used for land registration and property boundary definition.
-
B.
hasCadastralCode
Indicates that an entity is associated with a specific cadastral (land registry) identification code.
-
C.
hasMunicipalDistrict
Indicates that an administrative entity includes or is divided into one or more municipal districts as its subordinate units.
-
D.
isInMunicipality
Indicates that one entity (typically a place or address) is located within the administrative boundaries of a specific municipality.
-
E.
hasMunicipalUnitArea
Indicates that a municipal unit is associated with a specific measured area.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 21, 2026, 11:28 p.m.