Triple
T20319004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukes of Norfolk |
E492157
|
entity |
| Predicate | positionInPeerage |
P3784
|
FINISHED |
| Object | premier duke of England |
—
|
LITERAL FINISHED |
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: premier duke of England | Statement: [Dukes of Norfolk, positionInPeerage, premier duke of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPeerage Context triple: [Dukes of Norfolk, positionInPeerage, premier duke of England]
-
A.
rankRelativeToPeerage
Indicates how an entity’s hierarchical rank compares to that of a specified peer or peer group within a defined ranking system.
-
B.
rankInBritishPeerageSystem
chosen
Indicates the specific noble title or level an entity holds within the hierarchical structure of the British peerage system.
-
C.
typeOfPeerage
Indicates the specific rank or category within a system of peerage that a given title or noble status belongs to.
-
D.
regionOfPeerage
Indicates the geographic region or territorial area associated with a particular peerage title or rank.
-
E.
peerageSystem
Indicates a hierarchical system of noble ranks and titles that defines relative status and privileges among members of a nobility.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67789d8108190ae2e134f4b0b0be5 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b23a0788190bf1853ef5b81823f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:20 a.m.