Triple
T35368270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Saxe-Weimar-Eisenach |
E1021696
|
entity |
| Predicate | higherRankEquivalent |
P3584
|
FINISHED |
| Object | Grand Duke |
—
|
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: Grand Duke | Statement: [Duke of Saxe-Weimar-Eisenach, higherRankEquivalent, Grand Duke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherRankEquivalent Context triple: [Duke of Saxe-Weimar-Eisenach, higherRankEquivalent, Grand Duke]
-
A.
higherRankHas
Indicates that one entity holds a higher rank or hierarchical position than another entity.
-
B.
higherRankDescription
Indicates that one entity holds a superior or more senior rank or status compared to another entity.
-
C.
nextHigherRank
chosen
Indicates that one entity holds the immediately superior rank or level in a hierarchy relative to another entity.
-
D.
higherTierAlternative
Indicates that one option serves as a superior or more advanced alternative to another within a tiered structure.
-
E.
highestRanking
Indicates that one entity holds the top or most senior rank relative to a set of other entities.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:03 p.m.