Triple
T18656081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zambian pound |
E456067
|
entity |
| Predicate | replacedByDuring |
P24986
|
FINISHED |
| Object | 1960s–1970s currency reform |
—
|
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: 1960s–1970s currency reform | Statement: [Zambian pound, replacedByDuring, 1960s–1970s currency reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByDuring Context triple: [Zambian pound, replacedByDuring, 1960s–1970s currency reform]
-
A.
replacedDuring
chosen
Indicates that one entity took the place of another entity during a specified time period or interval.
-
B.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
C.
replacedByDuringRecovery
Indicates that one entity is substituted or superseded by another specifically for the duration of a recovery period.
-
D.
replacedBecause
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
E.
oftenReplacedBy
Indicates that one entity is frequently substituted or superseded by another in similar contexts or uses.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55084ca3481909ff3fd9045f25dcd |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.