Triple
T24796336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radclyffe family |
E620393
|
entity |
| Predicate | titleHeldWithinFamily |
P60633
|
FINISHED |
| Object | Earl of Sussex |
—
|
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 Sussex | Statement: [Radclyffe family, titleHeldWithinFamily, Earl of Sussex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHeldWithinFamily Context triple: [Radclyffe family, titleHeldWithinFamily, Earl of Sussex]
-
A.
titleHeldByFamily
chosen
Indicates that a particular title, rank, or honor is held collectively or traditionally by a specific family or family line.
-
B.
titleHeldFromFamily
Indicates that an entity holds a title that was inherited or passed down through their family lineage.
-
C.
higherTitleHeldBySameFamily
Indicates that a higher-ranking title is or was held by another member of the same family as the holder of the referenced title.
-
D.
currentTitleHolderFamily
Indicates that one family is the present holder of a particular title, position, or honor.
-
E.
titleHeldThrough
Indicates that an entity holds or possesses a title by means of, or via the intermediary of, another entity or mechanism.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 4:48 a.m.