Triple
T6037746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Haiti |
E134463
|
entity |
| Predicate | navalEnsignDesign |
P65132
|
FINISHED |
| Object | white field with Haitian flag in canton |
—
|
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: white field with Haitian flag in canton | Statement: [Flag of Haiti, navalEnsignDesign, white field with Haitian flag in canton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalEnsignDesign Context triple: [Flag of Haiti, navalEnsignDesign, white field with Haitian flag in canton]
-
A.
isWarEnsignOf
Indicates that one entity is the war ensign (a specific military or wartime flag) representing or belonging to another entity.
-
B.
isCivilEnsignOf
Indicates that an object is the civil (non-military) ensign or flag officially used to represent a particular entity, typically a country or territory.
-
C.
adoptedAsNavalEnsign
chosen
Indicates that something has been officially selected and put into use as a naval ensign (a flag or emblem representing a navy).
-
D.
civilFlagDesign
Indicates the design or pattern used on the civil (non-state) version of a flag.
-
E.
warFlagDesign
Indicates the design or pattern that appears on a group's war or battle 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056ccac948190a27547878d4db8e4 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.