Triple
T301938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Air Force Ensign defaced with ROC badge |
E6215
|
entity |
| Predicate | emblemPlacement |
P4762
|
FINISHED |
| Object | ROC badge in the fly |
—
|
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: ROC badge in the fly | Statement: [Royal Air Force Ensign defaced with ROC badge, emblemPlacement, ROC badge in the fly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblemPlacement Context triple: [Royal Air Force Ensign defaced with ROC badge, emblemPlacement, ROC badge in the fly]
-
A.
emblemFeatures
Indicates that an emblem includes or displays specific visual elements or characteristics.
-
B.
emblemStatus
Indicates the current state or condition of an emblem, such as whether it is active, valid, displayed, or in use.
-
C.
emblemLanguage
Indicates that an emblem (such as a symbol or logo) is associated with or presented in a particular language.
-
D.
primaryEmblem
Indicates that one emblem is the main or most representative symbol associated with an entity.
-
E.
hasOfficialInsigniaLocation
chosen
Indicates the specific place where an entity’s official insignia is physically located or displayed.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea2fba548190a5aeb1597dca96bd |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93c367881908d3f6e2b81d44d7f |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.