Triple
T1078352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tricolor flag of Bolivia |
E23889
|
entity |
| Predicate | usesCoatOfArmsVariant |
P23660
|
FINISHED |
| Object | state flag of Bolivia |
—
|
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: state flag of Bolivia | Statement: [tricolor flag of Bolivia, usesCoatOfArmsVariant, state flag of Bolivia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCoatOfArmsVariant Context triple: [tricolor flag of Bolivia, usesCoatOfArmsVariant, state flag of Bolivia]
-
A.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
B.
featuredUnionJackVariant
Indicates that an entity prominently displays or uses a specific variant of the Union Jack as a key identifying or decorative feature.
-
C.
coatOfArmsMotto
Indicates the phrase or motto that appears on or is officially associated with a particular coat of arms.
-
D.
coatOfArmsFeatures
Indicates that a coat of arms includes or displays specific symbols, colors, or design elements as part of its heraldic composition.
-
E.
nationalFlag
Indicates that one entity is the official national flag representing the other entity (a country or nation).
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b943b41481909b24050ca7e78971 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b80f0fb08190a19a50e38ae8f16c |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.