Triple
T17418643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | heraldic eagle (1986–2021) |
E423550
|
entity |
| Predicate | obverseOrReverse |
P127380
|
FINISHED |
| Object | reverse |
—
|
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: reverse | Statement: [heraldic eagle (1986–2021), obverseOrReverse, reverse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obverseOrReverse Context triple: [heraldic eagle (1986–2021), obverseOrReverse, reverse]
-
A.
obverseStyle
Indicates the artistic or design style used on the obverse (front) side of an object, such as a coin or medal.
-
B.
obverseText
Indicates the text that appears on the front (obverse) side of an object, typically a coin or medal.
-
C.
obverseDepiction
Indicates that one entity is depicted on the obverse (front) side of another, such as the front face of a coin or medal.
-
D.
obverseDesignIntroduced
Indicates that a particular obverse design (front side of an item, typically a coin or medal) was first put into official use at a specified time.
-
E.
obverseLegendPlacement
Indicates the spatial placement or arrangement of the legend (inscription or text) on the obverse side of an object, typically a coin or medal.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44234d840819096484a15d407785a |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:46 a.m.