Triple
T2659649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portrait Series banknotes |
E54695
|
entity |
| Predicate | includesPolymerNote |
P1393
|
FINISHED |
| Object | 2 Singapore dollars |
—
|
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: 2 Singapore dollars | Statement: [Portrait Series banknotes, includesPolymerNote, 2 Singapore dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPolymerNote Context triple: [Portrait Series banknotes, includesPolymerNote, 2 Singapore dollars]
-
A.
notableExtension
Indicates that one entity is a significant or prominent extension, add-on, or expansion of another entity.
-
B.
isNotedOn
Indicates that information about one entity is recorded, mentioned, or annotated on another entity (such as a document, record, or medium).
-
C.
includesAbstract
Indicates that one entity contains or incorporates the abstract or summary section of another entity.
-
D.
hasUsageNote
Indicates that there is an associated explanatory note describing how or when something should be used.
-
E.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd94f3b1881909bd36cfe61c254a5 |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.