Triple
T6507629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | His Imperial Highness |
E150049
|
entity |
| Predicate | typeOfRank |
P53396
|
FINISHED |
| Object | style rather than substantive title |
—
|
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: style rather than substantive title | Statement: [His Imperial Highness, typeOfRank, style rather than substantive title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRank Context triple: [His Imperial Highness, typeOfRank, style rather than substantive title]
-
A.
nobleRankType
chosen
Indicates the specific category or level of nobility associated with an entity within a hierarchical noble rank system.
-
B.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
C.
representsRank
Indicates that one entity serves as the rank, status, or hierarchical level assigned to another entity.
-
D.
isRank
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
-
E.
namedForRank
Indicates that something is named after a specific rank or title held by an entity.
- 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:43 p.m.