Triple
T1850255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Ferry Service |
E41377
|
entity |
| Predicate | hasPublicServiceObligation |
P6352
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Maine State Ferry Service, hasPublicServiceObligation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicServiceObligation Context triple: [Maine State Ferry Service, hasPublicServiceObligation, yes]
-
A.
hasCivicFunction
Indicates that an entity performs, is responsible for, or is associated with an official public or civic role, duty, or service.
-
B.
hasMunicipalService
chosen
Indicates that a municipality provides or is responsible for a specific public service to a given area, facility, or population.
-
C.
nationalService
Indicates that an entity performs or is obligated to perform service duties on behalf of a nation, typically in a governmental, military, or civic capacity.
-
D.
governmentServed
Indicates that a person has held a position serving in or working for a particular government.
-
E.
obligationType
Indicates the specific kind or category of duty, requirement, or commitment that applies within an obligation relationship.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdca6d8819083c66f3a29fd9fd1 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.