Triple
T29293821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miyazaki–Tokyo Haneda |
E742760
|
entity |
| Predicate | usesCurrencyRegion |
P18115
|
FINISHED |
| Object | Japanese yen area |
—
|
NE NERFINISHED |
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 area | Statement: [Miyazaki–Tokyo Haneda, usesCurrencyRegion, Japanese yen area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCurrencyRegion Context triple: [Miyazaki–Tokyo Haneda, usesCurrencyRegion, Japanese yen area]
-
A.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
B.
currencyArea
chosen
Indicates that one entity is the geographic or economic region in which the other entity’s currency is officially used or valid.
-
C.
usesCurrencyInitially
Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
-
D.
currencyScope
Indicates the range or jurisdiction within which a particular currency is valid, applicable, or intended to be used.
-
E.
currencyCountry
Indicates that a given currency is officially used as legal tender in a particular country.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 28, 2026, 1:04 p.m.