Triple
T25795232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German East African rupie |
E649660
|
entity |
| Predicate | metalUsedInCoins |
P73799
|
FINISHED |
| Object | copper |
—
|
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: copper | Statement: [German East African rupie, metalUsedInCoins, copper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metalUsedInCoins Context triple: [German East African rupie, metalUsedInCoins, copper]
-
A.
coinageType
Indicates the specific type or category of coinage associated with an entity, such as its denomination, series, or monetary classification.
-
B.
mediumOfCoinage
chosen
Indicates the material or substance used as the physical medium in which a coin or form of money is produced.
-
C.
metalContentPre1965
Indicates that something has the metal composition or standard that was used before the year 1965.
-
D.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
E.
authorizedCoinMetal
Indicates that a particular metal is officially approved for use in minting a given coin.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ff02f0948190b1e3cee38a97105d |
completed | May 2, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 6:29 a.m.