Triple
T29685512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bank of issue |
E751071
|
entity |
| Predicate | noteIssuanceScope |
P32986
|
FINISHED |
| Object | national |
—
|
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: national | Statement: [bank of issue, noteIssuanceScope, national]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noteIssuanceScope Context triple: [bank of issue, noteIssuanceScope, national]
-
A.
issuerScope
Indicates the range or domain of authority, responsibility, or applicability associated with the entity acting as the issuer in a given context.
-
B.
oftenIssuedAs
Indicates that one entity is frequently released, published, or distributed in the form of another entity.
-
C.
isIssuedFor
Indicates that something (such as a document, order, or item) has been formally created, authorized, or provided for a specific purpose, recipient, or use.
-
D.
issuerProduces
Indicates that an issuer creates, generates, or brings into existence a particular product, document, asset, or item.
-
E.
geographicScopeOfIssuers
chosen
Indicates the geographic region or area in which the referenced issuers are located or operate.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67290186481908e59be35101a1817 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:13 p.m.