Triple
T3178903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knight Grand Commander |
E66530
|
entity |
| Predicate | orderInsigniaFeatures |
P8639
|
FINISHED |
| Object | image of a five-pointed star |
—
|
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: image of a five-pointed star | Statement: [Knight Grand Commander, orderInsigniaFeatures, image of a five-pointed star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderInsigniaFeatures Context triple: [Knight Grand Commander, orderInsigniaFeatures, image of a five-pointed star]
-
A.
emblemFeatures
chosen
Indicates that an emblem includes or displays specific visual elements or characteristics.
-
B.
liveryFeature
Indicates a characteristic or design element that is part of a specific livery or external appearance scheme.
-
C.
hasTypeOfInsignia
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
D.
recognizesProtectiveEmblem
Indicates that an entity acknowledges and respects a designated protective emblem as carrying special protected status or immunity.
-
E.
coatOfArmsFeatures
Indicates that a coat of arms includes or displays specific symbols, colors, or design elements as part of its heraldic composition.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada69db2088190baa1305892eb148a |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.