Triple
T67499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bureau of Engraving and Printing |
E1344
|
entity |
| Predicate | supervisesProcess |
P1410
|
FINISHED |
| Object | design of U.S. banknotes |
—
|
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: design of U.S. banknotes | Statement: [Bureau of Engraving and Printing, supervisesProcess, design of U.S. banknotes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supervisesProcess Context triple: [Bureau of Engraving and Printing, supervisesProcess, design of U.S. banknotes]
-
A.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
B.
hasProcess
chosen
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
C.
advisoryProcess
Indicates a relationship where one party provides guidance, recommendations, or expert advice to another through a structured consultative process.
-
D.
executionBy
Indicates that one entity carries out or performs the execution (killing or implementation of a death sentence) of another entity.
-
E.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a2509b5a088190bb9d2b650aeb8bca |
completed | Feb. 28, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69a24ea749788190bc17865171ff909a |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.