Triple
T27603894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peaks Island ferry terminal |
E700125
|
entity |
| Predicate | hasRegularService |
P27954
|
FINISHED |
| Object | year-round ferry service |
—
|
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: year-round ferry service | Statement: [Peaks Island ferry terminal, hasRegularService, year-round ferry service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegularService Context triple: [Peaks Island ferry terminal, hasRegularService, year-round ferry service]
-
A.
hasRegularServicePattern
Indicates that an entity consistently follows a defined, recurring schedule or pattern of service over time.
-
B.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
C.
hasDailyService
chosen
Indicates that a service or operation occurs every day on a regular, scheduled basis.
-
D.
hasMaintenanceService
Indicates that an entity receives or is covered by a maintenance service provided by another entity.
-
E.
hasServiceStandard
Indicates that an entity is associated with, or governed by, a defined service standard specifying expected service levels or quality.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: April 27, 2026, 2:09 p.m.