Triple
T3790850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerrera |
E89641
|
entity |
| Predicate | ferryType |
P45739
|
FINISHED |
| Object | passenger ferry |
—
|
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 ferry | Statement: [Kerrera, ferryType, passenger ferry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ferryType Context triple: [Kerrera, ferryType, passenger ferry]
-
A.
hasFerryType
chosen
Indicates that an entity (such as a ferry route or service) is associated with a specific type or category of ferry.
-
B.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
C.
ferryRange
Indicates the maximum distance an aircraft can fly without payload or passengers, typically with full fuel, under specified conditions.
-
D.
ferryOperator
Indicates that one entity operates, manages, or runs a ferry service for another entity or in a particular context.
-
E.
hullType
Indicates the specific structural design or configuration of an object's hull, typically classifying how its outer body or shell is shaped or constructed.
- 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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecefa3608190a7a20ed6df6a64b2 |
completed | March 9, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69aee743c8d08190a9f9c97b836bd703 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.