Triple
T27001736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corran Narrows |
E680125
|
entity |
| Predicate | ferryOperatorAtLocation |
P5933
|
FINISHED |
| Object | Highland Council |
—
|
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: Highland Council | Statement: [Corran Narrows, ferryOperatorAtLocation, Highland Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ferryOperatorAtLocation Context triple: [Corran Narrows, ferryOperatorAtLocation, Highland Council]
-
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.
ferryTerminalName
Indicates the name assigned to a ferry terminal involved in the relationship or action.
-
D.
ferryServiceName
Indicates the specific name assigned to a ferry service operating between locations.
-
E.
hasNearbyFerryPort
Indicates that one location is situated close enough to another location that serves as a ferry port to be considered nearby.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 6:58 a.m.