Triple
T30075270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European peerage ranks |
E764300
|
entity |
| Predicate | hasHighestCommonRank |
P4202
|
FINISHED |
| Object | 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: duke | Statement: [European peerage ranks, hasHighestCommonRank, duke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestCommonRank Context triple: [European peerage ranks, hasHighestCommonRank, duke]
-
A.
hasLowestCommonRank
Indicates that two entities share a lowest (most specific) common level in a ranking or hierarchical system.
-
B.
containsRank
Indicates that one entity includes or encompasses another entity that has a specific rank or hierarchical level within it.
-
C.
higherRankHas
Indicates that one entity holds a higher rank or hierarchical position than another entity.
-
D.
highestRankIn
chosen
Indicates that one entity holds the top or most senior rank within a specified group, category, or context relative to other entities.
-
E.
hasComparableRank
Indicates that two entities hold positions or levels that are equivalent or similar in rank within a given hierarchy or system.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 29, 2026, 7:01 p.m.