Triple
T3063494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand pound |
E62049
|
entity |
| Predicate | centralBankRoleStart |
P40740
|
FINISHED |
| Object | 1934 |
—
|
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: 1934 | Statement: [New Zealand pound, centralBankRoleStart, 1934]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralBankRoleStart Context triple: [New Zealand pound, centralBankRoleStart, 1934]
-
A.
centralBank
Indicates that an entity functions as the primary monetary authority responsible for issuing currency and implementing monetary policy for a specific jurisdiction.
-
B.
previousMonetaryAuthority
Indicates that one entity served as the monetary authority immediately before another entity in a temporal sequence.
-
C.
monetaryPolicyManagedBy
Indicates that the responsibility for formulating, directing, or overseeing a monetary policy is held by a specific managing authority or institution.
-
D.
monetaryAuthorityEstablishedYear
chosen
Indicates the year in which a given monetary authority was formally established.
-
E.
monetaryAuthorityAbbreviation
Indicates the standard shortened form or acronym used to refer to a particular monetary authority.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9ea088fc819090b9d5bbcb268671 |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.