Triple
T1267973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treasurer of the United States |
E15644
|
entity |
| Predicate | signatureAppearsOn |
P18545
|
FINISHED |
| Object | United States paper money |
—
|
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 paper money | Statement: [Treasurer of the United States, signatureAppearsOn, United States paper money]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureAppearsOn Context triple: [Treasurer of the United States, signatureAppearsOn, United States paper money]
-
A.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
B.
signatureLocation
chosen
Indicates the place or position where a signature is written, recorded, or otherwise applied.
-
C.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
D.
signatureRole
Indicates the specific function or capacity in which an entity participates in a signing or signature-related action.
-
E.
signatureEvent
Indicates an event in which an entity formally signs or authorizes something, such as a document, agreement, or record.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c0396e048190b4e2d7aab19268b3 |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.