Triple
T37629145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Norfolk |
E936292
|
entity |
| Predicate | linkedToDukedom |
P75216
|
FINISHED |
| Object | Duke of Norfolk |
—
|
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: Duke of Norfolk | Statement: [Earl of Norfolk, linkedToDukedom, Duke of Norfolk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToDukedom Context triple: [Earl of Norfolk, linkedToDukedom, Duke of Norfolk]
-
A.
linkedDukedom
chosen
Indicates a relationship where one dukedom is formally connected or associated with another dukedom.
-
B.
reasonForDukedom
Indicates the justification or cause for which a dukedom is granted, held, or recognized.
-
C.
elevatedToDukedom
Indicates that an entity has been raised or promoted to the rank or title of a dukedom.
-
D.
holdsPremierDukedom
Indicates that an entity holds the highest-ranking or most senior dukedom within a given nobility system.
-
E.
grantedAsDuchyTo
Indicates that one party formally conferred the status, title, or territory of a duchy upon another party.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: May 3, 2026, 4:18 p.m.