Triple
T28791864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kvarken Archipelago |
E726975
|
entity |
| Predicate | transnationalSiteCountryPartner |
P72269
|
FINISHED |
| Object | Sweden |
—
|
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: Sweden | Statement: [Kvarken Archipelago, transnationalSiteCountryPartner, Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transnationalSiteCountryPartner Context triple: [Kvarken Archipelago, transnationalSiteCountryPartner, Sweden]
-
A.
partnerNation
Indicates that one entity is recognized as a collaborating or allied nation in relation to another entity.
-
B.
crossBorderPartner
chosen
Indicates a partnership relationship between entities that operate across national or jurisdictional borders.
-
C.
countryPartner
Indicates a formal partnership relationship between two countries, such as cooperation, alliance, or strategic collaboration.
-
D.
mainTradingPartnerCountry
Indicates the country that serves as the primary trading partner for a given entity, based on the largest or most significant volume of trade.
-
E.
cooperationPartner
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 28, 2026, 6:23 a.m.