Triple
T953973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grenadier Guards |
E20584
|
entity |
| Predicate | distinctiveInsignia |
P1617
|
FINISHED |
| Object | grenade badge |
—
|
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: grenade badge | Statement: [Grenadier Guards, distinctiveInsignia, grenade badge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distinctiveInsignia Context triple: [Grenadier Guards, distinctiveInsignia, grenade badge]
-
A.
protectiveEmblemName
Indicates that a given name is the designated title or label of a protective emblem associated with an entity or context.
-
B.
recognizesProtectiveEmblem
Indicates that an entity acknowledges and respects a designated protective emblem as carrying special protected status or immunity.
-
C.
hasTypeOfInsignia
chosen
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
D.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
E.
coatOfArmsMotto
Indicates the phrase or motto that appears on or is officially associated with a particular coat of arms.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3da8d508190b56b29d7f235d2c4 |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a045308190ab94f3adab40db8d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.