Triple
T35481589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Otaru |
E1025484
|
entity |
| Predicate | wasMajorPortInPeriod |
P62857
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [City of Otaru, wasMajorPortInPeriod, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMajorPortInPeriod Context triple: [City of Otaru, wasMajorPortInPeriod, late 19th century]
-
A.
wasFirstMajorSeaportOf
Indicates that one place served as the earliest significant seaport for another place or region.
-
B.
servedAsMainSeaportUntil
Indicates that an entity functioned as the primary seaport for another entity up to a specified point in time.
-
C.
isAmongLargestPortsIn
Indicates that a port ranks among the largest ports within a specified geographic or administrative area.
-
D.
isMajorSeaport
Indicates that a location functions as a primary maritime port handling significant volumes of sea-based trade, transport, or shipping activity.
-
E.
isHistoricPortOf
chosen
Indicates that a location served as a significant port for another place during a past historical period.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.