Triple
T18965555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Ensign of Canada |
E464028
|
entity |
| Predicate | officiallyAuthorizedAsCivilEnsign |
P32467
|
FINISHED |
| Object | 1892 |
—
|
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: 1892 | Statement: [Red Ensign of Canada, officiallyAuthorizedAsCivilEnsign, 1892]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officiallyAuthorizedAsCivilEnsign Context triple: [Red Ensign of Canada, officiallyAuthorizedAsCivilEnsign, 1892]
-
A.
isCivilEnsignOf
chosen
Indicates that an object is the civil (non-military) ensign or flag officially used to represent a particular entity, typically a country or territory.
-
B.
adoptedAsNavalEnsign
Indicates that something has been officially selected and put into use as a naval ensign (a flag or emblem representing a navy).
-
C.
isWarEnsignOf
Indicates that one entity is the war ensign (a specific military or wartime flag) representing or belonging to another entity.
-
D.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
-
E.
isOnFlagOf
Indicates that something (typically a symbol, image, or design element) appears on or is depicted on a flag.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d663948190b496fbd2e69c7f43 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon