Triple
T203523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Bank Note |
E4558
|
entity |
| Predicate | formatChange |
P130
|
FINISHED |
| Object | switched to small-size notes in 1929 |
—
|
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: switched to small-size notes in 1929 | Statement: [National Bank Note, formatChange, switched to small-size notes in 1929]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatChange Context triple: [National Bank Note, formatChange, switched to small-size notes in 1929]
-
A.
formatAfter
Indicates that one entity’s format or structural arrangement is derived from, follows, or is applied subsequent to another entity’s format.
-
B.
formatBefore
Indicates that one item’s format or formatting must occur or be applied prior to another item’s format or formatting.
-
C.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
D.
functionChange
Indicates that an entity’s function, role, or operational behavior has been altered from one state or purpose to another.
-
E.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f46b4f081909e5ee3718109a71f |
completed | Feb. 28, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69a25b4b42ec8190bef16bbbdd30a742 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.