Triple
T34491730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Derby |
E885485
|
entity |
| Predicate | requiresPeerageTitle |
P121828
|
FINISHED |
| Object | Earl of Derby must exist |
—
|
LITERAL FINISHED |
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: Earl of Derby must exist | Statement: [Lady Derby, requiresPeerageTitle, Earl of Derby must exist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPeerageTitle Context triple: [Lady Derby, requiresPeerageTitle, Earl of Derby must exist]
-
A.
hasPeerageTitle
Indicates that an entity holds or is associated with a formal noble or aristocratic title within a peerage system.
-
B.
hasPeerageType
Indicates that an entity holds or is associated with a specific category or rank of peerage (noble title).
-
C.
hasRankOrTitle
Indicates that an entity holds, is assigned, or is associated with a specific rank, title, or formal designation.
-
D.
nobleRankRequired
chosen
Indicates that a certain minimum noble rank or title is required for the related action, status, or relationship to apply.
-
E.
hasHonoraryTitle
Indicates that an entity has been granted a formal honorary title or distinction, typically in recognition of merit or achievement.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
Created at: May 1, 2026, 2:01 a.m.