Triple
T4045904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagoya Stock Exchange |
E84064
|
entity |
| Predicate | typicalTradingCurrency |
P13920
|
FINISHED |
| Object | Japanese yen |
—
|
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: Japanese yen | Statement: [Nagoya Stock Exchange, typicalTradingCurrency, Japanese yen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTradingCurrency Context triple: [Nagoya Stock Exchange, typicalTradingCurrency, Japanese yen]
-
A.
isMostTradedCurrency
Indicates that a currency is the one with the highest trading volume or frequency in a given market or context.
-
B.
majorCurrencyPair
Indicates that the two currencies form a widely traded, highly liquid foreign-exchange pair considered significant in global markets.
-
C.
isMajorTradingCurrencyIn
chosen
Indicates that a currency is one of the primary or most significant currencies used for trade within a specified market or region.
-
D.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
E.
currencyDepicted
Indicates that one entity visually represents or shows the image or symbol of a particular currency on it.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb6135b481909d2be890a2140ff9 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.