Triple
T31687451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clifford family of Ugbrooke |
E808697
|
entity |
| Predicate | typeOfEstateConnection |
P201516
|
FINISHED |
| Object | hereditary family seat |
—
|
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: hereditary family seat | Statement: [Clifford family of Ugbrooke, typeOfEstateConnection, hereditary family seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEstateConnection Context triple: [Clifford family of Ugbrooke, typeOfEstateConnection, hereditary family seat]
-
A.
hasEstateType
Indicates that an entity possesses or is associated with a particular category or type of estate.
-
B.
countryEstateType
Indicates the classification or category of an estate based on the country in which it is located or to which it belongs.
-
C.
relationshipBetweenHouses
Indicates a relational connection or association that exists between two or more houses.
-
D.
hasAssociatedEstate
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
-
E.
connectsTypeOfPlace
Indicates a relationship where one place is linked or associated with another based on its type or category of location.
- F. None of above. chosen
Provenance (4 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69ffff2533248190ac291f5f2e858320 |
completed | May 10, 2026, 3:44 a.m. |
Created at: April 30, 2026, 11:07 p.m.