Triple
T11630536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Upper Austria |
E276383
|
entity |
| Predicate | coatOfArmsDexterField |
P32838
|
FINISHED |
| Object | golden eagle sable |
—
|
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: golden eagle sable | Statement: [Flag of Upper Austria, coatOfArmsDexterField, golden eagle sable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coatOfArmsDexterField Context triple: [Flag of Upper Austria, coatOfArmsDexterField, golden eagle sable]
-
A.
fieldForCrossTincture
Indicates that a field (background area) is designated to receive a cross tincture (coloring or pattern) in a heraldic design.
-
B.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
C.
regionOfHeraldry
Indicates a relationship where a heraldic symbol, coat of arms, or emblem is associated with or belongs to a specific geographic or administrative region.
-
D.
heraldicCharge
chosen
Indicates that one entity serves as a heraldic charge, i.e., a symbolic figure or emblem placed on another entity’s coat of arms or shield.
-
E.
coatOfArmsCaption
Indicates the descriptive text that explains or labels the depicted coat of arms.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a127b2688190ae3a340f851e834b |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:39 p.m.