Triple
T450662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Chile |
E7118
|
entity |
| Predicate | colorWhiteSymbolism |
P129
|
FINISHED |
| Object | snow of the Andes |
—
|
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: snow of the Andes | Statement: [Coat of arms of Chile, colorWhiteSymbolism, snow of the Andes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorWhiteSymbolism Context triple: [Coat of arms of Chile, colorWhiteSymbolism, snow of the Andes]
-
A.
colors
Indicates that one entity assigns, describes, or provides the color or colors of another entity.
-
B.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
C.
colorOftenUsed
Indicates that a particular color is frequently used or commonly applied in relation to something.
-
D.
whiteStripeMeaning
Indicates that one entity has a white stripe pattern or marking that is significant or characteristic in the context of the relationship.
-
E.
colorCharge
Indicates a relationship where an entity possesses a specific quantum color charge (such as red, green, or blue) in the context of strong nuclear interactions.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef691cc8819091729eaac52c9457 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2ede3187c8190a7ced078f0ec3476 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.