Triple
T37665779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Kingdom |
E937816
|
entity |
| Predicate | hasCurrencyShape |
P190499
|
FINISHED |
| Object | coin shaped like a manhole cover |
—
|
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: coin shaped like a manhole cover | Statement: [Metro Kingdom, hasCurrencyShape, coin shaped like a manhole cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrencyShape Context triple: [Metro Kingdom, hasCurrencyShape, coin shaped like a manhole cover]
-
A.
depictedOnCurrencyOf
Indicates that one entity is visually represented or featured on the currency issued by another entity.
-
B.
isLegalTenderFor
Indicates that a particular currency or form of money is officially recognized by a governing authority as valid payment for debts and financial transactions within a specified jurisdiction.
-
C.
currencyDepicted
Indicates that one entity visually represents or shows the image or symbol of a particular currency on it.
-
D.
hasBankCharacteristic
Indicates that a bank possesses a particular attribute, feature, or quality.
-
E.
usesCurrencyMotif
chosen
Indicates that something incorporates or features currency-related imagery, symbols, or themes as a central motif.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 3, 2026, 4:18 p.m.