Triple
T33449938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Saxony-Anhalt |
E856607
|
entity |
| Predicate | colorsRelatedTo |
P65875
|
FINISHED |
| Object | German national colors |
—
|
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: German national colors | Statement: [Coat of arms of Saxony-Anhalt, colorsRelatedTo, German national colors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorsRelatedTo Context triple: [Coat of arms of Saxony-Anhalt, colorsRelatedTo, German national colors]
-
A.
colors
Indicates that one entity assigns, describes, or provides the color or colors of another entity.
-
B.
associatedColour
chosen
Indicates that one entity is linked to another as its characteristic or representative colour.
-
C.
colorCompatibility
Indicates whether the colors associated with the entities can be used together harmoniously or without conflict.
-
D.
colorIndicates
Indicates that a particular color serves as a sign, marker, or signal conveying specific information or status about something.
-
E.
colorTheory
Indicates a relationship where principles or concepts about how colors interact, combine, or affect perception are applied or referenced between entities.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:37 a.m.