Triple
T33429413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Largs Harbour |
E856083
|
entity |
| Predicate | ferryServicesOperatedBy |
P5933
|
FINISHED |
| Object | Caledonian MacBrayne |
—
|
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: Caledonian MacBrayne | Statement: [Largs Harbour, ferryServicesOperatedBy, Caledonian MacBrayne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ferryServicesOperatedBy Context triple: [Largs Harbour, ferryServicesOperatedBy, Caledonian MacBrayne]
-
A.
ferryOperator
chosen
Indicates that one entity operates, manages, or runs a ferry service for another entity or in a particular context.
-
B.
ferryOperatorType
Indicates the type or category of operator responsible for running a ferry service.
-
C.
ferryServiceName
Indicates the specific name assigned to a ferry service operating between locations.
-
D.
ferryNetworkBrand
Indicates the brand or commercial identity under which a ferry network operates or is marketed.
-
E.
ferryFlightCarrier
Indicates that one carrier operates a ferry (non-revenue repositioning) flight on behalf of another carrier.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e47f37848190aadb137c81760f1f |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.