Triple
T36678504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Line suburbs |
E905608
|
entity |
| Predicate | currentlyServedBy |
P56872
|
FINISHED |
| Object | SEPTA Paoli/Thorndale Line |
—
|
NE NERFINISHED |
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: SEPTA Paoli/Thorndale Line | Statement: [Main Line suburbs, currentlyServedBy, SEPTA Paoli/Thorndale Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentlyServedBy Context triple: [Main Line suburbs, currentlyServedBy, SEPTA Paoli/Thorndale Line]
-
A.
presentlyServedBy
chosen
Indicates that an entity is currently being provided with service or attended to by another entity.
-
B.
mayBeServedBy
Indicates that one entity is a possible or permissible provider or server of another entity, without asserting that the service actually occurs.
-
C.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
D.
isServedOn
Indicates that one item (typically food or drink) is presented or provided atop or together with a particular surface, container, or accompaniment.
-
E.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:12 p.m.