Triple
T32933891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMN |
E842473
|
entity |
| Predicate | honourRankType |
P175250
|
FINISHED |
| Object | Grand Commander class |
—
|
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 Commander class | Statement: [SMN, honourRankType, Grand Commander class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honourRankType Context triple: [SMN, honourRankType, Grand Commander class]
-
A.
honourType
Indicates the specific category or classification of an honour or award associated with an entity.
-
B.
honorRank
chosen
Indicates a hierarchical relationship where one entity holds a particular level or position of honor or prestige relative to others.
-
C.
nobleRankType
Indicates the specific category or level of nobility associated with an entity within a hierarchical noble rank system.
-
D.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
E.
honourTypeContext
Indicates the specific situational or cultural context in which an honour or form of respect is expressed or applies.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d10722e88190bb59c5768ce23d43 |
completed | May 3, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.