Triple
T13577423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eisenhower dollar |
E324323
|
entity |
| Predicate | featuresInscription |
P34998
|
FINISHED |
| Object | LIBERTY |
—
|
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: LIBERTY | Statement: [Eisenhower dollar, featuresInscription, LIBERTY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresInscription Context triple: [Eisenhower dollar, featuresInscription, LIBERTY]
-
A.
inscriptionFeature
chosen
Indicates that one entity bears or contains an inscribed element or marking that is treated as a notable feature in relation to another entity.
-
B.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
-
C.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
D.
issuedInscription
Indicates that an authority or source formally created and released a specific inscription or written record.
-
E.
hasInscriptions
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02de1988190af2d473973ecd529 |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.