Triple
T10603480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peenestrom |
E275810
|
entity |
| Predicate | locatedOnMainlandSide |
P67139
|
FINISHED |
| Object | Vorpommern mainland |
—
|
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: Vorpommern mainland | Statement: [Peenestrom, locatedOnMainlandSide, Vorpommern mainland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnMainlandSide Context triple: [Peenestrom, locatedOnMainlandSide, Vorpommern mainland]
-
A.
terminalOnMainland
Indicates that a transportation or service terminal is physically located on the mainland rather than on an island or offshore location.
-
B.
connectedToMainlandBy
Indicates that one landmass or area is physically linked to a mainland, typically via a bridge, causeway, or other continuous connection.
-
C.
appliesToMainland
chosen
Indicates that something is relevant or applicable specifically to the mainland portion of a territory, excluding its islands or overseas areas.
-
D.
nearCityOnSingaporeSide
Indicates that one entity is located close to a city that lies on the Singapore side of a relevant boundary or region.
-
E.
locatedOnTerritoryOf
Indicates that one entity is situated within or on the land area governed or owned by another entity.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4992248190b640d743ccf02c82 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:32 p.m.