Triple
T27508240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of New Mexico |
E694335
|
entity |
| Predicate | vexillologyNotability |
P162464
|
FINISHED |
| Object | noted for simplicity and symbolism |
—
|
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: noted for simplicity and symbolism | Statement: [Flag of New Mexico, vexillologyNotability, noted for simplicity and symbolism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vexillologyNotability Context triple: [Flag of New Mexico, vexillologyNotability, noted for simplicity and symbolism]
-
A.
vexillologicalCategory
Indicates the classification of something within a specific category or type used in the study of flags.
-
B.
vexillologyCode
Indicates a standardized code or classification assigned within the context of flags or the study of flags (vexillology).
-
C.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
-
D.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
E.
flagDesignSymbolism
Indicates the symbolic meanings or concepts represented by elements in a flag’s design.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ef65ca88190b3e3b1c91d668843 |
completed | May 2, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:14 p.m.