Triple
T23564279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Territorial Decoration |
E579326
|
entity |
| Predicate | locationOfNameEngraving |
P48678
|
FINISHED |
| Object | reverse of the decoration |
—
|
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 of the decoration | Statement: [Territorial Decoration, locationOfNameEngraving, reverse of the decoration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfNameEngraving Context triple: [Territorial Decoration, locationOfNameEngraving, reverse of the decoration]
-
A.
hasEngravableArea
chosen
Indicates that an object possesses a surface or region suitable for being engraved.
-
B.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
-
C.
hasNumberOfNamesInscribed
Indicates the quantity of distinct names that are inscribed on a given entity.
-
D.
inscribedUnderName
Indicates that text is written or engraved directly beneath a specified name, typically as a label, dedication, or explanatory inscription.
-
E.
mintEngravingContext
Indicates the contextual relationship between a mint and the engraving activity or process associated with it.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6b04cc81909385e485b8bdd54b |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:33 p.m.