Triple
T18236373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kettleby |
E436686
|
entity |
| Predicate | hasHeritageConservationFocus |
P4776
|
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: [Kettleby, hasHeritageConservationFocus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageConservationFocus Context triple: [Kettleby, hasHeritageConservationFocus, true]
-
A.
hasHeritageFocus
Indicates that something is primarily concerned with, dedicated to, or centered around heritage-related themes, values, or preservation.
-
B.
hasHeritageValueFor
Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
-
C.
heritageManagement
chosen
Indicates the management, preservation, and regulation of cultural or natural heritage resources by responsible entities.
-
D.
isPartOfHeritage
Indicates that something belongs to, contributes to, or is recognized as a component of a broader cultural, historical, or natural heritage.
-
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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b69a688190b140961eb298c36e |
completed | April 19, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:33 a.m.