Triple
T34067775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northbourne, Kent |
E873674
|
entity |
| Predicate | hasHistoricManor |
P9779
|
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: [Northbourne, Kent, hasHistoricManor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricManor Context triple: [Northbourne, Kent, hasHistoricManor, true]
-
A.
hasManorHouse
chosen
Indicates that one entity possesses or is associated with a manor house as a property or feature.
-
B.
hasHistoricPremises
Indicates that an entity possesses or is associated with premises that have historical significance or heritage value.
-
C.
containsHistoricHouse
Indicates that one entity includes or encompasses a historic house within its boundaries or composition.
-
D.
hasHistoricHut
Indicates that an entity possesses, contains, or is associated with a historic hut.
-
E.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: May 1, 2026, 1:52 a.m.