Triple
T6873298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leopold V, Duke of Austria |
E158604
|
entity |
| Predicate | coat of arms influence |
P73857
|
FINISHED |
| Object | red-white-red Austrian flag tradition |
—
|
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: red-white-red Austrian flag tradition | Statement: [Leopold V, Duke of Austria, coat of arms influence, red-white-red Austrian flag tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coat of arms influence Context triple: [Leopold V, Duke of Austria, coat of arms influence, red-white-red Austrian flag tradition]
-
A.
hasHeraldicUse
Indicates that something is used as, or incorporated into, a heraldic device, emblem, or coat of arms.
-
B.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
C.
coatOfArmsOnFlag
Indicates that a flag features or displays a particular coat of arms as part of its design.
-
D.
coatOfArmsType
Indicates the specific kind or category of coat of arms associated with an entity.
-
E.
coatOfArmsFeatures
Indicates that a coat of arms includes or displays specific symbols, colors, or design elements as part of its heraldic composition.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8c73ea08190b6bb1463e7ead47b |
completed | March 27, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b363dc8190a7225b540ab2bc40 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:22 p.m.