Triple
T36568976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lister family |
E902061
|
entity |
| Predicate | propertyTypeHistoricallyHeld |
P114979
|
FINISHED |
| Object | rural estates |
—
|
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: rural estates | Statement: [Lister family, propertyTypeHistoricallyHeld, rural estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyTypeHistoricallyHeld Context triple: [Lister family, propertyTypeHistoricallyHeld, rural estates]
-
A.
estateTypeHistorically
chosen
Indicates that one entity historically had a particular type or classification of estate, even if that estate type may have changed or no longer exists in the present.
-
B.
propertyHeld
Indicates that a particular property is possessed, owned, or controlled by a specified entity.
-
C.
housingTypeHistoric
Indicates that an entity’s housing type is classified based on historical or heritage-related characteristics.
-
D.
propertyTypeOwned
Indicates that one entity owns a specific type or category of property in relation to another entity.
-
E.
hasHistoricPremises
Indicates that an entity possesses or is associated with premises that have historical significance or heritage value.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.