Triple
T9139317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heroic Military College |
E219280
|
entity |
| Predicate | emblemRepresents |
P72227
|
FINISHED |
| Object | Mexican Army traditions |
—
|
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: Mexican Army traditions | Statement: [Heroic Military College, emblemRepresents, Mexican Army traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblemRepresents Context triple: [Heroic Military College, emblemRepresents, Mexican Army traditions]
-
A.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
B.
emblematicFor
chosen
Indicates that something serves as a representative symbol or characteristic example of something else.
-
C.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
-
D.
emblemUsedBy
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
-
E.
emblemFeatures
Indicates that an emblem includes or displays specific visual elements or characteristics.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8f129c08190b6f053984cb7363f |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:19 p.m.