Triple
T30329154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cunliffe-Lister |
E771424
|
entity |
| Predicate | hasAristocraticBranch |
P13166
|
FINISHED |
| Object | Swinton line |
—
|
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: Swinton line | Statement: [Cunliffe-Lister, hasAristocraticBranch, Swinton line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAristocraticBranch Context triple: [Cunliffe-Lister, hasAristocraticBranch, Swinton line]
-
A.
hasBranchOfImperialFamily
Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
-
B.
aristocraticOrigin
Indicates that an entity originates from, or is derived from, an aristocratic or noble background.
-
C.
hasRelativeInAristocracy
Indicates that an entity has at least one relative who belongs to the aristocracy or noble class.
-
D.
dynasticBranch
chosen
Indicates a genealogical relationship where one lineage or house originates from, or is a subordinate offshoot of, a larger parent dynasty.
-
E.
hasRoyalAncestryFrom
Indicates that one entity possesses royal lineage or descent originating from another entity.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 29, 2026, 7:53 p.m.