Triple
T19869602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Łódź Voivodeship |
E477477
|
entity |
| Predicate | usesHeraldicColors |
P61212
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Flag of Łódź Voivodeship, usesHeraldicColors, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHeraldicColors Context triple: [Flag of Łódź Voivodeship, usesHeraldicColors, yes]
-
A.
heraldicColor
Indicates that one entity specifies or bears a particular heraldic color in a coat of arms or related heraldic context.
-
B.
usesHeraldicStyle
Indicates that one entity employs or follows the heraldic style, conventions, or visual language associated with another entity.
-
C.
hasHeraldicUse
chosen
Indicates that something is used as, or incorporated into, a heraldic device, emblem, or coat of arms.
-
D.
hasHeraldicMeaning
Indicates that something (typically a symbol, color, or design) carries a specific meaning or significance within the system of heraldry.
-
E.
hasHeraldicBasis
Indicates that something is founded on, derived from, or justified by heraldic principles, symbols, or traditions.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658a2cc8481908d134b0b5cf79d06 |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.