Triple
T25252654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svaneke Lighthouse |
E632783
|
entity |
| Predicate | seaServed |
P158071
|
FINISHED |
| Object | Baltic Sea |
—
|
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: Baltic Sea | Statement: [Svaneke Lighthouse, seaServed, Baltic Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaServed Context triple: [Svaneke Lighthouse, seaServed, Baltic Sea]
-
A.
servesCoast
Indicates that one entity provides transportation, protection, or other services along or for the benefit of a particular coastline.
-
B.
served
Indicates that one entity provided a service, assistance, or role-based function to or for another entity.
-
C.
servedHarbour
Indicates that an entity provided service, support, or functions related to a harbour or port.
-
D.
servedStrained
Indicates that something is provided or presented after having been filtered or strained to remove solids or impurities.
-
E.
servedShip
Indicates that one entity performed service or duty aboard, or in direct support of, a particular ship.
- 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4808cf89881909c7d9ee9c42216c4 |
completed | May 1, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 1:11 p.m.