Triple
T6807440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Fairfax, 2nd Lord Fairfax of Cameron |
E156343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Fairfax family |
C21667
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: member of the Fairfax family Context triple: [Thomas Fairfax, 2nd Lord Fairfax of Cameron, instanceOf, member of the Fairfax family]
-
A.
member of the Cavendish family
A member of the Cavendish family is an individual belonging by birth or legal relation to the historically prominent Cavendish lineage, known for its political influence, aristocratic status, and cultural contributions.
-
B.
member of the Clive family
A member of the Clive family is an individual who belongs by blood, marriage, or adoption to the familial lineage identified by the Clive surname and its shared history, traditions, and relationships.
-
C.
member of the Grenville family
A member of the Grenville family is an individual belonging by birth, marriage, or adoption to the historically notable Grenville lineage, sharing its name, heritage, and familial ties.
-
D.
member of the Hepburn family
A member of the Hepburn family is an individual who belongs by birth, marriage, or adoption to the familial lineage identified by the Hepburn surname.
-
E.
member of the Winthrop family
A member of the Winthrop family is an individual belonging by birth, marriage, or adoption to the historically prominent Winthrop lineage, sharing its familial identity, heritage, and social ties.
- F. None of above. chosen
Provenance (1 batch)
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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:16 p.m.