Triple
T22565355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uffelte |
E557933
|
entity |
| Predicate | hasHistoricRuralCharacter |
P103583
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Uffelte, hasHistoricRuralCharacter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricRuralCharacter Context triple: [Uffelte, hasHistoricRuralCharacter, true]
-
A.
hasHistoricParishCharacter
Indicates that something possesses the distinctive qualities or attributes traditionally associated with a historic parish.
-
B.
isHistoricRuralCommunity
chosen
Indicates that a community is located in a rural area and holds recognized historical significance or heritage value.
-
C.
containsHistoricHouse
Indicates that one entity includes or encompasses a historic house within its boundaries or composition.
-
D.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
-
E.
hasHeritageUse
Indicates that something is used, managed, or valued in a way that relates to cultural, historical, or natural heritage.
- 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15fa9ebc8819098d74fb41e14bd7e |
completed | April 29, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:52 p.m.