Triple
T4017180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kleeblatt |
E91190
|
entity |
| Predicate | visualIdentityElement |
P48662
|
FINISHED |
| Object | green cloverleaf |
—
|
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: green cloverleaf | Statement: [Kleeblatt, visualIdentityElement, green cloverleaf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualIdentityElement Context triple: [Kleeblatt, visualIdentityElement, green cloverleaf]
-
A.
visualIdentityDesigner
Indicates that an entity is responsible for creating or shaping the visual identity or visual branding of another entity.
-
B.
visualTrademark
Indicates that one entity serves as a visual trademark or logo representing another entity.
-
C.
hasBrandIdentityElement
chosen
Indicates that an entity includes or is associated with a specific component of its overall brand identity (such as a logo, color scheme, or tagline).
-
D.
symbolOnInsignia
Indicates that a particular symbol appears on or is featured as part of an insignia.
-
E.
visualElements
Indicates that one entity contains, uses, or is characterized by specific visual components or graphical features associated with another entity.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.