Triple
T794277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Point Mint |
E16982
|
entity |
| Predicate | mintStatusGranted |
P19211
|
FINISHED |
| Object | 1988 |
—
|
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: 1988 | Statement: [West Point Mint, mintStatusGranted, 1988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mintStatusGranted Context triple: [West Point Mint, mintStatusGranted, 1988]
-
A.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
B.
hasMandate
Indicates that an entity is officially authorized or required to perform a specific role, action, or set of responsibilities.
-
C.
grantedTo
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
-
D.
styleGranted
Indicates that a particular style, manner, or mode of expression has been conferred or authorized for use by one entity to another.
-
E.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a79b976c819085cd381bbd597ca5 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a510f61881909175d6d8719246cd |
completed | March 1, 2026, 8:44 p.m. |
| PDg | Predicate description generation | batch_69a4a5edd0248190bd0240e5b3e67c71 |
completed | March 1, 2026, 8:47 p.m. |
Created at: March 1, 2026, 7:38 p.m.