Triple
T1059949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knight or Dame Commander |
E22882
|
entity |
| Predicate | honoursType |
P4123
|
FINISHED |
| Object | order of chivalry grade |
—
|
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: order of chivalry grade | Statement: [Knight or Dame Commander, honoursType, order of chivalry grade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoursType Context triple: [Knight or Dame Commander, honoursType, order of chivalry grade]
-
A.
honourType
chosen
Indicates the specific category or classification of an honour or award associated with an entity.
-
B.
honoursSystem
Indicates that an entity follows or complies with a particular system of rules, standards, or principles.
-
C.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
D.
honourTypeContext
Indicates the specific situational or cultural context in which an honour or form of respect is expressed or applies.
-
E.
mainHonoursLists
Indicates that one entity serves as the primary or official list of honours associated with another 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4ba6e35ac8190802341c31bda0e3b |
completed | March 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69a4b7340a048190807363f19d17a58f |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.