Triple
T30687189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osborne ducal line |
E781217
|
entity |
| Predicate | heldDukedom |
P96984
|
FINISHED |
| Object | Dukedom of Leeds |
—
|
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: Dukedom of Leeds | Statement: [Osborne ducal line, heldDukedom, Dukedom of Leeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldDukedom Context triple: [Osborne ducal line, heldDukedom, Dukedom of Leeds]
-
A.
holdsPremierDukedom
Indicates that an entity holds the highest-ranking or most senior dukedom within a given nobility system.
-
B.
heldByBeforeDukedom
Indicates that an entity held a particular title, position, or role prior to being granted a dukedom.
-
C.
heldEarldom
Indicates that a person possessed and held the noble title and rank of an earl.
-
D.
wasDukeOf
chosen
Indicates that a person held the hereditary noble title and ruling position of duke over a specified territory or domain.
-
E.
elevatedToDukedom
Indicates that an entity has been raised or promoted to the rank or title of a dukedom.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b85bc58819098fb53ffa72d570a |
completed | May 2, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:33 p.m.