Triple
T10149959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEPTA Cynwyd Line |
E232606
|
entity |
| Predicate | statusBeyondCynwyd |
P92514
|
FINISHED |
| Object | passenger service discontinued |
—
|
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 service discontinued | Statement: [SEPTA Cynwyd Line, statusBeyondCynwyd, passenger service discontinued]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusBeyondCynwyd Context triple: [SEPTA Cynwyd Line, statusBeyondCynwyd, passenger service discontinued]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
statusInUK
Indicates the legal or official status that an entity holds within the United Kingdom (e.g., immigration, residency, or authorization category).
-
C.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
D.
statusRecordedBy
Indicates that the status of an entity was documented or captured by a specific agent or system.
-
E.
statusAfter1832
Indicates the status or condition of an entity as it existed after the year 1832.
- 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_69ca84885e48819088a31b127cf44904 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec03e80c81909c813dae91c56272 |
completed | April 2, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd51bc440c819086320900701f87c2 |
completed | April 1, 2026, 5:11 p.m. |
Created at: March 30, 2026, 9:08 p.m.