Triple
T21580953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Bavaria |
E532519
|
entity |
| Predicate | people'sCrownFeatures |
P144342
|
FINISHED |
| Object | five visible leaves |
—
|
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: five visible leaves | Statement: [Coat of arms of Bavaria, people'sCrownFeatures, five visible leaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: people'sCrownFeatures Context triple: [Coat of arms of Bavaria, people'sCrownFeatures, five visible leaves]
-
A.
crownCharacteristic
Indicates that an entity has a particular property, feature, or quality specifically associated with its crown.
-
B.
crownDepicted
Indicates that one entity visually represents or shows a crown associated with another entity.
-
C.
featuresMuralCrown
Indicates that something includes or displays a mural crown as one of its features or attributes.
-
D.
crownRepresents
Indicates that one entity (the crown) symbolically stands for, embodies, or serves as an official emblem of another entity, such as authority, sovereignty, or a governing body.
-
E.
crownType
Indicates the specific style or form of a crown associated with an entity.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb5c496c819093113dd5790fca48 |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:31 p.m.