Triple
T26477840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugh de Chaworth |
E666087
|
entity |
| Predicate | clanOrHouse |
P134637
|
FINISHED |
| Object | House of Chaworth |
—
|
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: House of Chaworth | Statement: [Hugh de Chaworth, clanOrHouse, House of Chaworth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanOrHouse Context triple: [Hugh de Chaworth, clanOrHouse, House of Chaworth]
-
A.
clanFamilyOf
chosen
Indicates that one entity belongs to, descends from, or is otherwise affiliated with the same clan or extended family group as another entity.
-
B.
clanType
Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
-
C.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
D.
notableClans
Indicates that there exists a significant or historically important clan associated with the subject.
-
E.
clanInheritance
Indicates that rights, titles, or property are passed down within a clan according to its internal rules of succession.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612ce613081908f37874b9ecfe7cc |
completed | May 2, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:24 a.m.