Triple
T6646802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chemulpo |
E150720
|
entity |
| Predicate | openedAsTreatyPort |
P5295
|
FINISHED |
| Object | 1883 |
—
|
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: 1883 | Statement: [Chemulpo, openedAsTreatyPort, 1883]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsTreatyPort Context triple: [Chemulpo, openedAsTreatyPort, 1883]
-
A.
openedPortToForeignTrade
chosen
Indicates that an entity has allowed or enabled a port to conduct commercial trade with foreign countries.
-
B.
openedAsEmbassy
Indicates that a diplomatic mission or office was formally inaugurated and began operating with the status of an embassy.
-
C.
openedPort
Indicates that a network port on a host or device is currently open and able to accept incoming connections.
-
D.
linkedToTreaty
Indicates that an entity has a formal connection or association with a specific treaty, such as being established by, governed by, or otherwise related to that treaty.
-
E.
treatyConcluded
Indicates that a formal agreement or treaty has been officially finalized and brought into force between the involved parties.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2 p.m.