Triple
T26587641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wels District |
E667252
|
entity |
| Predicate | hasStatutoryCityEnclave |
P3366
|
FINISHED |
| Object | Wels |
—
|
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: Wels | Statement: [Wels District, hasStatutoryCityEnclave, Wels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatutoryCityEnclave Context triple: [Wels District, hasStatutoryCityEnclave, Wels]
-
A.
isMunicipalEnclave
Indicates that one municipality is entirely surrounded by, and geographically enclosed within, another municipality.
-
B.
hasMunicipalPart
Indicates that an administrative or territorial entity includes a municipality as one of its constituent parts.
-
C.
hasMunicipalDistrict
Indicates that an administrative entity includes or is divided into one or more municipal districts as its subordinate units.
-
D.
isSubProvincialCity
Indicates that a city holds a sub-provincial administrative status, ranking below a province but above ordinary prefecture-level cities in the governmental hierarchy.
-
E.
hasIndependentCity
chosen
Indicates that a larger administrative region or entity contains a city that is administratively independent from the surrounding local jurisdictions.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 27, 2026, 2:06 a.m.