Triple
T514550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yokohama |
E10676
|
entity |
| Predicate | openedToForeignTrade |
P5295
|
FINISHED |
| Object | 1859 |
—
|
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: 1859 | Statement: [Yokohama, openedToForeignTrade, 1859]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedToForeignTrade Context triple: [Yokohama, openedToForeignTrade, 1859]
-
A.
openedPortToForeignTrade
chosen
Indicates that an entity has allowed or enabled a port to conduct commercial trade with foreign countries.
-
B.
usedInInternationalTrade
Indicates that something participates as a good, service, or instrument in commercial exchanges between different countries.
-
C.
isLinkedEconomicallyTo
Indicates that two entities are connected through economic relationships such as trade, investment, financial flows, or shared market dependencies.
-
D.
percentageOfWorldTrade
Indicates the proportion of total global trade that is accounted for by a particular entity or group.
-
E.
exportedTo
Indicates that goods, services, or resources are sent out from one entity or region to another for trade or sale.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f232fa688190b08a2fe3f22c7a6e |
completed | Feb. 28, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69a2f013c05481909e6dc87e7b20ebd8 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.