Triple
T27146770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedford family |
E681970
|
entity |
| Predicate | notableBranchTitle |
P57950
|
FINISHED |
| Object | Marquess of Tavistock |
—
|
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: Marquess of Tavistock | Statement: [Bedford family, notableBranchTitle, Marquess of Tavistock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBranchTitle Context triple: [Bedford family, notableBranchTitle, Marquess of Tavistock]
-
A.
notableBranch
Indicates that one entity is a particularly significant or prominent subdivision, offshoot, or branch of another entity.
-
B.
notableFork
Indicates that one entity is a significant fork or derivative version of another, typically diverging in a notable or influential way from the original.
-
C.
hasTitleBranch
Indicates that an entity holds or is associated with a specific title within a particular branch, division, or subdivision of an organization or structure.
-
D.
notableTitleOnTheLine
Indicates that a significant or prestigious title is at stake or being contested in the associated event or context.
-
E.
branchLabel
chosen
Indicates the label or name assigned to a specific branch within a hierarchical or branching structure.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
Created at: April 27, 2026, 9:11 a.m.