Triple
T4445770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wadern |
E96280
|
entity |
| Predicate | hasTownRights |
P43827
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Wadern, hasTownRights, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTownRights Context triple: [Wadern, hasTownRights, yes]
-
A.
grantedTownRights
Indicates that an authority formally conferred municipal or town privileges and legal status upon a settlement.
-
B.
hasTownStatus
chosen
Indicates that an entity possesses the legal or administrative status of being recognized as a town.
-
C.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
-
D.
hasTownship
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
-
E.
majorAccessTown
Indicates that a location serves as a primary or significant access point to a town, such as a main route, gateway, or connection hub.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d1eba08190899d0a3c1684ce4e |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.