Triple
T34772668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Lowther |
E1002408
|
entity |
| Predicate | usedAsCourtesyTitleByHeirOf |
P81246
|
FINISHED |
| Object | Earl of Lonsdale |
—
|
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: Earl of Lonsdale | Statement: [Viscount Lowther, usedAsCourtesyTitleByHeirOf, Earl of Lonsdale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCourtesyTitleByHeirOf Context triple: [Viscount Lowther, usedAsCourtesyTitleByHeirOf, Earl of Lonsdale]
-
A.
usedAsCourtesyTitleFor
chosen
Indicates that one entity serves as a courtesy title or honorific form of address applied to another entity.
-
B.
heirApparentTitleUsedUntil
Indicates that a specific title was used by an heir apparent up until a particular point in time or event.
-
C.
usedAsCourtesyTitleWithin
Indicates that a term or title is employed as a polite or honorific form of address within a particular context, culture, or setting.
-
D.
recognizedHeirTitle
Indicates that an individual is formally acknowledged as the legitimate holder or successor of a specific hereditary title.
-
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_69f76db30a108190bb57ca95b873e5bb |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: May 3, 2026, 3:59 p.m.