Triple
T3107170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cotuit |
E64858
|
entity |
| Predicate | notServedBy |
P3875
|
FINISHED |
| Object | passenger rail |
—
|
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 rail | Statement: [Cotuit, notServedBy, passenger rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notServedBy Context triple: [Cotuit, notServedBy, passenger rail]
-
A.
doesNotServe
chosen
Indicates that one entity explicitly does not provide a service, function, or role to another entity.
-
B.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
C.
notImplementedBy
Indicates that a specified functionality, specification, or feature is *not* realized or provided by the referenced entity (such as a system, component, or implementation).
-
D.
alsoServedBy
Indicates that the same service, function, or role is additionally provided or fulfilled by another entity alongside the primary one.
-
E.
notRecognizedBy
Indicates that one entity does not acknowledge, accept, or formally recognize the status, authority, or validity of another entity.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29d4aa8819093287bc71370fc05 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.