Triple
T1850267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Ferry Service |
E41377
|
entity |
| Predicate | ownedRollingStock |
P34147
|
FINISHED |
| Object | ferry vessels |
—
|
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: ferry vessels | Statement: [Maine State Ferry Service, ownedRollingStock, ferry vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedRollingStock Context triple: [Maine State Ferry Service, ownedRollingStock, ferry vessels]
-
A.
formerRollingStock
Indicates that an entity was previously used as rolling stock (e.g., railway vehicles) but no longer serves in that capacity.
-
B.
usesRollingStock
Indicates that one entity employs or operates specific rolling stock (such as rail vehicles) in its activities or services.
-
C.
rollingStockType
Indicates the specific category or type of railway rolling stock associated with an entity (e.g., locomotive, passenger car, freight wagon).
-
D.
introducedRollingStock
Indicates that an entity caused new rolling stock (such as trains or rail vehicles) to be put into service or use.
-
E.
usesRollingStockOwner
Indicates that one entity operates or employs rolling stock (such as trains or rail vehicles) that is owned by another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69abb32a8d548190a231c7c2ce276a5e |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:33 p.m.