Triple
T5839711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MNT |
E129559
|
entity |
| Predicate | hasCurrencySymbolPlacement |
P2875
|
FINISHED |
| Object | after amount in Mongolian notation |
—
|
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: after amount in Mongolian notation | Statement: [MNT, hasCurrencySymbolPlacement, after amount in Mongolian notation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrencySymbolPlacement Context triple: [MNT, hasCurrencySymbolPlacement, after amount in Mongolian notation]
-
A.
hasCurrencySignPlacement
chosen
Indicates where the currency sign is positioned relative to the numeric amount in a monetary value.
-
B.
currencyAppearance
Indicates how a currency physically looks or is visually represented, such as its design, color, or format.
-
C.
currencySymbol
Indicates the symbol used to represent a particular currency in written or printed form.
-
D.
replacedCurrencySymbol
Indicates that one currency symbol has been substituted or superseded by another in a given context.
-
E.
currencyNumber
Indicates the numerical value or denomination associated with a specific currency.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.