Triple
T3601051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of Colombia |
E76255
|
entity |
| Predicate | PhrygianCapSymbolizes |
P129
|
FINISHED |
| Object | liberty |
—
|
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: liberty | Statement: [coat of arms of Colombia, PhrygianCapSymbolizes, liberty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PhrygianCapSymbolizes Context triple: [coat of arms of Colombia, PhrygianCapSymbolizes, liberty]
-
A.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
B.
clothingSymbolism
Indicates how clothing or attire conveys symbolic meaning, such as status, identity, emotion, or cultural significance, within a given context.
-
C.
chapeau
Indicates that one entity serves as a hat or head covering worn by another entity.
-
D.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
E.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1a1e8c48190a28ea3ddfe8c4e54 |
completed | March 8, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.