Triple
T19062355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capped Bust dime |
E466563
|
entity |
| Predicate | reverseOrientation |
P9300
|
FINISHED |
| Object | heraldic eagle design |
—
|
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: heraldic eagle design | Statement: [Capped Bust dime, reverseOrientation, heraldic eagle design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reverseOrientation Context triple: [Capped Bust dime, reverseOrientation, heraldic eagle design]
-
A.
reverseFeature
Indicates that one feature is the inverse or opposite counterpart of another feature in a given context.
-
B.
reversed
chosen
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
C.
exportOrientation
Indicates that an entity’s activities, production, or strategy are primarily directed toward serving foreign or international markets rather than domestic ones.
-
D.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
E.
orientationInducedBy
Indicates that the orientation of one entity is determined or caused by the orientation or configuration 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e195ac048190a57b57e585d022d4 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.