Triple
T28986138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of the Province of Jujuy |
E734686
|
entity |
| Predicate | hasSealOrSymbol |
P94983
|
FINISHED |
| Object | coat of arms of Jujuy Province |
—
|
NE NERFINISHED |
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: coat of arms of Jujuy Province | Statement: [Government of the Province of Jujuy, hasSealOrSymbol, coat of arms of Jujuy Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSealOrSymbol Context triple: [Government of the Province of Jujuy, hasSealOrSymbol, coat of arms of Jujuy Province]
-
A.
isSealOf
chosen
Indicates that one entity serves as the official seal, emblem, or stamp that authenticates, endorses, or formally represents another entity.
-
B.
usesSealImage
Indicates that one entity employs or incorporates the seal image of another entity in some context or medium.
-
C.
usedSeal
Indicates that an entity has applied or employed a seal (e.g., for closure, authentication, or protection) on another entity.
-
D.
hasDateOnSeal
Indicates that a seal bears or includes a specific date as part of its inscription or design.
-
E.
hasTribalSeal
Indicates that an entity bears, is marked with, or is officially associated with a specific tribal seal.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: April 28, 2026, 9:14 a.m.