Triple
T12538152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polstead |
E299757
|
entity |
| Predicate | hasHistoricCountrysideSetting |
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: [Polstead, hasHistoricCountrysideSetting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricCountrysideSetting Context triple: [Polstead, hasHistoricCountrysideSetting, true]
-
A.
hasHistoricVillageArea
Indicates that an entity includes or is associated with an area recognized as a historic village or traditional settlement zone.
-
B.
isHistoricRuralCommunity
chosen
Indicates that a community is located in a rural area and holds recognized historical significance or heritage value.
-
C.
containsHistoricTown
Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
-
D.
hasHeritageUse
Indicates that something is used, managed, or valued in a way that relates to cultural, historical, or natural heritage.
-
E.
hasHistoricHut
Indicates that an entity possesses, contains, or is associated with a historic hut.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.