Triple
T29073603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukes of Somerset |
E735873
|
entity |
| Predicate | lowerPrecedenceThan |
P13059
|
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: [Dukes of Somerset, lowerPrecedenceThan, Duke of Norfolk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerPrecedenceThan Context triple: [Dukes of Somerset, lowerPrecedenceThan, Duke of Norfolk]
-
A.
hasLowerPrecedenceThan
chosen
Indicates that one item is ranked or ordered with a lower priority or importance compared to another item.
-
B.
lowestPrecedenceSide
Indicates that one side in a relationship, operation, or comparison has the lowest precedence relative to other sides involved.
-
C.
orderOfPrecedenceHigher
Indicates that one entity holds a higher rank or priority than another in an established order of precedence.
-
D.
hasPrecedence
Indicates that one entity occurs, is considered, or is applied before another in order, priority, or importance.
-
E.
bindingPrecedent
Indicates that a prior decision or ruling must be followed as an authoritative legal standard in deciding a current case.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 10:21 a.m.