Triple
T28571524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treasury Department circular |
E723124
|
entity |
| Predicate | documentTypeOf |
P105928
|
FINISHED |
| Object | United States government publication |
—
|
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: United States government publication | Statement: [Treasury Department circular, documentTypeOf, United States government publication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentTypeOf Context triple: [Treasury Department circular, documentTypeOf, United States government publication]
-
A.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
B.
documentTypeUsed
Indicates that a particular type or category of document is employed or applied in a given context or activity.
-
C.
DOCType
chosen
Indicates the type or category of a document associated with an entity or action.
-
D.
documentsTypeOfStructure
Indicates that an entity records or specifies the particular type or classification of a structure.
-
E.
documentTypeContext
Indicates the contextual relationship between a document and its specific type or classification within a given setting or usage scenario.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 4:10 a.m.