Triple
T38033375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweden–Finland border |
E948976
|
entity |
| Predicate | meetsCountriesAt |
P189884
|
FINISHED |
| Object | Norway |
—
|
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: Norway | Statement: [Sweden–Finland border, meetsCountriesAt, Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsCountriesAt Context triple: [Sweden–Finland border, meetsCountriesAt, Norway]
-
A.
meetsInCountry
Indicates that two or more entities have an in-person meeting that takes place within the specified country.
-
B.
meetsInCountrySubdivision
Indicates that two or more entities meet or have a meeting within a specific administrative subdivision of a country (such as a state, province, or region).
-
C.
confluenceCountry
Indicates the country within whose territory a given confluence (meeting point of geographic coordinates or rivers) is located.
-
D.
LänderRepresentedIn
Indicates that certain countries have official representation or presence within a specified entity or context.
-
E.
meetsBetween
Indicates that one entity meets or encounters another at some point between two specified reference points or times.
- F. None of above. chosen
Provenance (4 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fc44c67118819088accfeded7b449e |
completed | May 7, 2026, 7:52 a.m. |
Created at: May 3, 2026, 4:20 p.m.