Triple
T26472272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Marlborough |
E665933
|
entity |
| Predicate | traditionalFamily |
P180207
|
FINISHED |
| Object | Spencer-Churchill family |
—
|
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: Spencer-Churchill family | Statement: [Duchess of Marlborough, traditionalFamily, Spencer-Churchill family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalFamily Context triple: [Duchess of Marlborough, traditionalFamily, Spencer-Churchill family]
-
A.
topFamily
Indicates that the subject entity belongs to the highest-ranking or primary family group within a given hierarchy or classification.
-
B.
traditionalSubfamily
Indicates that one group is classified as a subfamily of another under a traditional (historical or non-revised) taxonomic system.
-
C.
cultFamily
Indicates that one entity is a family member of another within the context of a cult or cult-like group.
-
D.
familyType
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
-
E.
family
Indicates a familial relationship or connection between entities, such as being related by blood, marriage, or adoption.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 27, 2026, 12:20 a.m.