Triple
T25104144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of the Basque Country |
E628820
|
entity |
| Predicate | hasSaltire |
P159720
|
FINISHED |
| Object | green saltire |
—
|
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: green saltire | Statement: [flag of the Basque Country, hasSaltire, green saltire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSaltire Context triple: [flag of the Basque Country, hasSaltire, green saltire]
-
A.
hasInescutcheon
Indicates that one heraldic shield or coat of arms bears another smaller shield (an inescutcheon) placed upon it.
-
B.
principalTartanOf
Indicates that one entity is the officially recognized primary tartan associated with another entity, such as a clan, organization, or region.
-
C.
royalStandard
Indicates that an entity is the official royal flag or emblem used to represent a monarch or royal authority.
-
D.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
E.
hasHeraldicSubject
Indicates that one entity serves as the heraldic subject or emblematic figure depicted on another entity, such as on a coat of arms or shield.
- F. None of above. chosen
Provenance (4 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5f7a205688190b8f36bff5013247c |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 18, 2026, 6:26 a.m.