Triple
T179161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Reserve Note |
E3645
|
entity |
| Predicate | formerDenomination |
P4004
|
FINISHED |
| Object | $500 |
—
|
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: $500 | Statement: [Federal Reserve Note, formerDenomination, $500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerDenomination Context triple: [Federal Reserve Note, formerDenomination, $500]
-
A.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
-
B.
previousDenomination
chosen
Indicates that one entity was the earlier or former denomination (name, value, or classification) of another entity in a sequence of denominations.
-
C.
denomination
Indicates the specific religious or organizational branch, sect, or subgroup with which an entity is affiliated.
-
D.
centralToDenomination
Indicates that something is a core or defining element within a particular religious denomination.
-
E.
previousCurrency
Indicates that one currency served as the predecessor or was replaced by another currency in a monetary system or sequence.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a25900709c8190a65e778936be5dd5 |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2566b53d481909c0ed40dd3719e8c |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.