Triple
T25104148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of the Basque Country |
E628820
|
entity |
| Predicate | adoptedAsOfficialFlag |
P73975
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [flag of the Basque Country, adoptedAsOfficialFlag, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedAsOfficialFlag Context triple: [flag of the Basque Country, adoptedAsOfficialFlag, 1979]
-
A.
adoptedAsNationalFlagOn
Indicates that an entity was officially chosen and put into use as a country's national flag on a specific date.
-
B.
officialFlagOf
Indicates that one entity is the formally recognized flag that represents another entity (such as a country, organization, or region).
-
C.
adoptedAsRegionalFlagInCountry
chosen
Indicates that a flag has been officially adopted for use as a regional flag within a specific country.
-
D.
adoptedAsNavalEnsign
Indicates that something has been officially selected and put into use as a naval ensign (a flag or emblem representing a navy).
-
E.
adoptedAsEmblemBy
Indicates that something has been officially chosen and used as a symbolic emblem by a particular entity or group.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4656bddb4819088650eefd5ef837a |
completed | May 1, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:26 a.m.