Triple
T12985654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America the Beautiful Quarters |
E321759
|
entity |
| Predicate | mintMarksUsed |
P17363
|
FINISHED |
| Object | P |
—
|
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: P | Statement: [America the Beautiful Quarters, mintMarksUsed, P]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mintMarksUsed Context triple: [America the Beautiful Quarters, mintMarksUsed, P]
-
A.
mintMarkUsedOn
chosen
Indicates that a particular mint mark was applied to or appears on a specific coin or numismatic item.
-
B.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
-
C.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
D.
usedReportingMarks
Indicates that an entity employed specific railroad reporting marks to identify rolling stock or operations.
-
E.
reportedMarks
Indicates that an entity has formally communicated or submitted the marks/grades of another entity (such as a student or assessment) to a relevant party or system.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:40 p.m.