Triple
T18279961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Bullion Coin Act of 1985 |
E437837
|
entity |
| Predicate | typeOfProgramCreated |
P2192
|
FINISHED |
| Object | bullion coin program |
—
|
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: bullion coin program | Statement: [Gold Bullion Coin Act of 1985, typeOfProgramCreated, bullion coin program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfProgramCreated Context triple: [Gold Bullion Coin Act of 1985, typeOfProgramCreated, bullion coin program]
-
A.
createdProgram
Indicates that an entity authored, developed, or produced a particular program (such as software or a coded application).
-
B.
programType
chosen
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
C.
typeOfProject
Indicates the specific category or kind of project that an entity is associated with or classified under.
-
D.
producedProgram
Indicates that one entity created or produced a specific program (such as a TV show, software, or other structured content).
-
E.
acronymOfCreatedProgram
Indicates that one entity is the acronym or abbreviated name of a program that was created or developed as represented by the other entity.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50055d2b88190a10199771f64c4b9 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.