Triple
T31402400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spodsbjerg |
E801033
|
entity |
| Predicate | isOnEastCoastOf |
P83964
|
FINISHED |
| Object | Langeland |
—
|
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: Langeland | Statement: [Spodsbjerg, isOnEastCoastOf, Langeland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnEastCoastOf Context triple: [Spodsbjerg, isOnEastCoastOf, Langeland]
-
A.
representsCountryOnAtlanticCoast
Indicates that the subject serves as a representative (such as a diplomat, organization, or official body) for a country that is located on the Atlantic Ocean coast.
-
B.
isInNortheasternUS
Indicates that a location or entity is situated within the northeastern region of the United States.
-
C.
isCoastalDestinationFor
Indicates that a place serves as a seaside or ocean-adjacent travel destination for a particular person, group, or market.
-
D.
isCoastalOn
Indicates that one entity is located along or directly borders the coastline of another entity (such as a body of water or sea).
-
E.
locatedOnEasternShoreOf
chosen
Indicates that one entity is situated on the eastern shore or bank of another geographic feature, such as a body of water or landform.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 29, 2026, 9:20 p.m.