Triple
T24556837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Bornholm |
E607537
|
entity |
| Predicate | vexillologyType |
P58469
|
FINISHED |
| Object | Nordic cross flag |
—
|
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: Nordic cross flag | Statement: [Flag of Bornholm, vexillologyType, Nordic cross flag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vexillologyType Context triple: [Flag of Bornholm, vexillologyType, Nordic cross flag]
-
A.
vexillologicalCategory
chosen
Indicates the classification of something within a specific category or type used in the study of flags.
-
B.
vexillologyCode
Indicates a standardized code or classification assigned within the context of flags or the study of flags (vexillology).
-
C.
coatOfArmsType
Indicates the specific kind or category of coat of arms associated with an entity.
-
D.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
-
E.
flagDesign
Indicates the relationship in which one entity is responsible for creating, specifying, or defining the design of a flag associated with 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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f2af7c8190904f247ef29121d0 |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.