Triple
T24719790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papiermark |
E612263
|
entity |
| Predicate | highDenominationNotes |
P74833
|
FINISHED |
| Object | trillion-mark notes |
—
|
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: trillion-mark notes | Statement: [Papiermark, highDenominationNotes, trillion-mark notes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highDenominationNotes Context triple: [Papiermark, highDenominationNotes, trillion-mark notes]
-
A.
highDenomination
chosen
Indicates that something has a relatively large or high face value compared to other items in the same category (e.g., currency, stamps, or tokens).
-
B.
higherDenomination
Indicates that one entity represents a monetary value that is greater than the monetary value represented by another entity.
-
C.
banknoteDenomination
Indicates the specific face value assigned to a banknote in a given currency.
-
D.
statusOfHighDenominations
Indicates the current condition, availability, or regulatory standing of high-denomination units (such as large-value currency or instruments) within a system or context.
-
E.
hasBanknotes
Indicates that an entity possesses or contains one or more banknotes.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:40 a.m.