Triple
T29861038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnett family |
E758315
|
entity |
| Predicate | historicEstate |
P114979
|
FINISHED |
| Object | Leys |
—
|
NE NERFINISHED |
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: Leys | Statement: [Burnett family, historicEstate, Leys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicEstate Context triple: [Burnett family, historicEstate, Leys]
-
A.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
-
B.
historicHomeGround
Indicates that a location has traditionally served as the primary or long-standing home venue for a team, organization, or group.
-
C.
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.
-
D.
housingTypeHistoric
Indicates that an entity’s housing type is classified based on historical or heritage-related characteristics.
-
E.
historicalHabitat
Indicates that an entity previously lived, occurred, or was distributed within a particular habitat or environment in the past.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69febce5877c8190a5e000ef5331ec88 |
completed | May 9, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69febad1cd588190abc7686bcb39a371 |
completed | May 9, 2026, 4:40 a.m. |
Created at: April 29, 2026, 5:49 p.m.