Triple
T179171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Reserve Note |
E3645
|
entity |
| Predicate | reverseFeatures |
P1603
|
FINISHED |
| Object | vignette or symbolic imagery |
—
|
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: vignette or symbolic imagery | Statement: [Federal Reserve Note, reverseFeatures, vignette or symbolic imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reverseFeatures Context triple: [Federal Reserve Note, reverseFeatures, vignette or symbolic imagery]
-
A.
reverseInscription
Indicates that one entity is inscribed as the reverse or mirror image of another entity’s inscription.
-
B.
reflects
Indicates that one entity (often a surface, medium, or representation) throws back, mirrors, or otherwise shows an image, property, or state of another entity.
-
C.
featuresText
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
-
D.
badgeReverseDesign
chosen
Indicates the design or imagery that appears on the reverse (back) side of a badge.
-
E.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a25900709c8190a65e778936be5dd5 |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2566b53d481909c0ed40dd3719e8c |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.