Triple
T20842856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seal of the State of Georgia |
E513143
|
entity |
| Predicate | reverseSymbolizes |
P142053
|
FINISHED |
| Object | commerce |
—
|
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: commerce | Statement: [Seal of the State of Georgia, reverseSymbolizes, commerce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reverseSymbolizes Context triple: [Seal of the State of Georgia, reverseSymbolizes, commerce]
-
A.
restoredSymbol
Indicates that an entity has been brought back or reinstated as a symbol after having been altered, removed, or lost.
-
B.
reverseInscription
Indicates that one entity is inscribed as the reverse or mirror image of another entity’s inscription.
-
C.
reverseFeature
Indicates that one feature is the inverse or opposite counterpart of another feature in a given context.
-
D.
symbolizedIn
Indicates that one entity serves as a symbol or representation of another entity.
-
E.
mountSymbolizes
Indicates that a mount (such as a horse, vehicle, or rideable creature) serves as a symbolic representation of something else, such as status, role, or affiliation.
- 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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34cdf9881909f3340874bbee5bc |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:43 p.m.