Triple
T25070331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cholmondeley family |
E627889
|
entity |
| Predicate | hasTraditionalResidenceType |
P162560
|
FINISHED |
| Object | castle |
—
|
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: castle | Statement: [Cholmondeley family, hasTraditionalResidenceType, castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalResidenceType Context triple: [Cholmondeley family, hasTraditionalResidenceType, castle]
-
A.
hasTraditionalResidenceType
chosen
Indicates that an entity is associated with a particular customary or historically established type of residence.
-
B.
hasTraditionalResidenceCountry
Indicates that an entity’s customary or long-term country of residence is the specified country.
-
C.
hasAncestralResidence
Indicates that an entity has a residence or dwelling place that belonged to or was established by its ancestors.
-
D.
hasCanonicalResidence
Indicates that an entity has an officially recognized primary place of residence or domicile.
-
E.
traditionallyResidesIn
Indicates that an entity customarily lives or has its long-established home in a particular place or region.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 6:10 a.m.