Triple
T7803961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Nuevo León |
E180500
|
entity |
| Predicate | containsHeraldicShield |
P61212
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Flag of Nuevo León, containsHeraldicShield, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsHeraldicShield Context triple: [Flag of Nuevo León, containsHeraldicShield, yes]
-
A.
hasHeraldicShieldShape
Indicates that an entity’s heraldic shield is characterized by a specific geometric or stylistic shape.
-
B.
hasHeraldicSubject
Indicates that one entity serves as the heraldic subject or emblematic figure depicted on another entity, such as on a coat of arms or shield.
-
C.
hasHeraldicRole
Indicates that an entity holds or is assigned a specific role or function within a heraldic context (such as in coats of arms, armorial bearings, or heraldic ceremonies).
-
D.
hasHeraldicAttitude
Indicates that an entity (typically an animal or figure in heraldry) is depicted with a specific standardized posture or stance in a coat of arms.
-
E.
hasHeraldicUse
chosen
Indicates that something is used as, or incorporated into, a heraldic device, emblem, or coat of arms.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:34 p.m.