Triple
T31393118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oban ferry terminal |
E800788
|
entity |
| Predicate | connectedByServiceType |
P74738
|
FINISHED |
| Object | passenger ferries |
—
|
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: passenger ferries | Statement: [Oban ferry terminal, connectedByServiceType, passenger ferries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedByServiceType Context triple: [Oban ferry terminal, connectedByServiceType, passenger ferries]
-
A.
connectsServiceType
Indicates a relationship where one entity is linked or associated to another based on a specific type of service connection.
-
B.
linkedByServiceTo
chosen
Indicates that one entity is connected or associated with another through a specific service acting as the linking mechanism.
-
C.
connectsDeviceType
Indicates a relationship where one entity is associated with or linked to a specific type or category of device.
-
D.
relatedService
Indicates that one service is connected or associated with another service in a relevant or dependent way.
-
E.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: April 29, 2026, 9:19 p.m.