Triple
T37118433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neukirchen |
E919182
|
entity |
| Predicate | hasCadastralStatus |
P128277
|
FINISHED |
| Object | cadastral community |
—
|
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: cadastral community | Statement: [Neukirchen, hasCadastralStatus, cadastral community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCadastralStatus Context triple: [Neukirchen, hasCadastralStatus, cadastral community]
-
A.
hasCadastralCode
Indicates that an entity is associated with a specific cadastral (land registry) identification code.
-
B.
hasCadastralArea
Indicates that an entity possesses or is associated with a specific cadastral (official land registry) area measurement.
-
C.
hasLandStatus
Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
-
D.
legalStatusInPlot
Indicates the legal standing or rights an entity holds within the context of a specific plot or storyline.
-
E.
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.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fff328ddc0819080642334a41fcf95 |
completed | May 10, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69fff2e0971c819081aa66f4a6a34b28 |
completed | May 10, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4:15 p.m.