Triple
T26194776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Stanley |
E655067
|
entity |
| Predicate | isHeirApparentTitleOf |
P2940
|
FINISHED |
| Object | Earldom of Derby |
—
|
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: Earldom of Derby | Statement: [Lord Stanley, isHeirApparentTitleOf, Earldom of Derby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHeirApparentTitleOf Context triple: [Lord Stanley, isHeirApparentTitleOf, Earldom of Derby]
-
A.
hasHeirApparentTitle
Indicates that an entity holds a title designating them as the officially recognized heir apparent to another entity’s position or rank.
-
B.
heirApparentOf
chosen
Indicates that one entity is the officially recognized primary successor who is expected to inherit a title, position, or role from another entity.
-
C.
lastHeirApparentUsingTitle
Indicates that the subject is the most recent person to have held the status of heir apparent while using a specified title.
-
D.
consideredHeirApparent
Indicates that one entity is regarded or treated as the likely or expected successor to another entity, typically in a position of authority or inheritance.
-
E.
nobleTitleHeirTo
Indicates that one entity is the designated heir to the noble title held by 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60ca50d0081909d146f3c697227aa |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:46 p.m.