Triple
T7001614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss flag |
E162349
|
entity |
| Predicate | ensignDesign |
P21497
|
FINISHED |
| Object | white cross on red rectangular field |
—
|
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 cross on red rectangular field | Statement: [Swiss flag, ensignDesign, white cross on red rectangular field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ensignDesign Context triple: [Swiss flag, ensignDesign, white cross on red rectangular field]
-
A.
symbolOnInsignia
chosen
Indicates that a particular symbol appears on or is featured as part of an insignia.
-
B.
symbolDesigned
Indicates that one entity created or planned the design of a symbolic representation (such as a logo, icon, or emblem) for another entity.
-
C.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
-
D.
flagDesigner
Indicates that one entity is the person or group responsible for designing the flag associated with another entity.
-
E.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc0f8830819091f4356296234713 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.