Triple
T38235635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America’s Beautiful National Parks Quarter Dollar Coin Act of 2008 |
E1013612
|
entity |
| Predicate | designSelectionBasis |
P23142
|
FINISHED |
| Object | one site from each state |
—
|
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: one site from each state | Statement: [America’s Beautiful National Parks Quarter Dollar Coin Act of 2008, designSelectionBasis, one site from each state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designSelectionBasis Context triple: [America’s Beautiful National Parks Quarter Dollar Coin Act of 2008, designSelectionBasis, one site from each state]
-
A.
designSelectionBy
Indicates that a particular design or option has been chosen or determined by a specific agent or process.
-
B.
designCriteria
Indicates the standards, requirements, or constraints that guide how something should be planned, structured, or created.
-
C.
designSelectedIn
Indicates that a particular design has been chosen or picked out within a specific context, set, or selection process.
-
D.
decisionBasis
chosen
Indicates the underlying reason, criterion, or rationale on which a decision is made.
-
E.
reasonForDesign
Indicates that one entity serves as the explanation, motivation, or justification for why another entity was designed or created in a particular way.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
Created at: May 3, 2026, 4:30 p.m.