Triple
T26365862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inselbahn Langeoog |
E660328
|
entity |
| Predicate | isAccessibleOnlyBy |
P158909
|
FINISHED |
| Object | ferry connection |
—
|
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: ferry connection | Statement: [Inselbahn Langeoog, isAccessibleOnlyBy, ferry connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAccessibleOnlyBy Context triple: [Inselbahn Langeoog, isAccessibleOnlyBy, ferry connection]
-
A.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
B.
reachableOnlyBy
chosen
Indicates that one entity can be accessed or arrived at exclusively through another specific entity or route, with no alternative paths available.
-
C.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
D.
accessibleWithin
Indicates that one entity can be reached, used, or entered from within the spatial or contextual bounds of another entity.
-
E.
accessibleAs
Indicates that one entity can be reached, used, or obtained through another entity, often as an alternative form, route, or representation.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6102c248c8190886da68d61d006dc |
completed | May 2, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:55 p.m.