Triple
T14561315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copenhagen Malmö Port |
E341670
|
entity |
| Predicate | transnational |
P1499
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Copenhagen Malmö Port, transnational, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transnational Context triple: [Copenhagen Malmö Port, transnational, true]
-
A.
transboundaryContext
Indicates a context, situation, or effect that crosses or involves the boundaries between two or more distinct jurisdictions, regions, or territories.
-
B.
maintainsTransnationalTies
Indicates that an entity sustains ongoing social, economic, political, or cultural connections that span across national borders.
-
C.
intercontinental
Indicates a relationship or action that spans or connects multiple continents.
-
D.
transiting
Indicates that an entity is in the process of passing through, across, or between locations or states, typically as part of a journey or transfer.
-
E.
isInternational
chosen
Indicates that something has a connection to, involves, or extends across more than one 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb389d0f48190a1d9d69456d1cbe1 |
completed | April 14, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.