Triple
T24591040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newtown Branch |
E608537
|
entity |
| Predicate | formerServiceBeyond |
P43939
|
FINISHED |
| Object | Fox Chase station |
—
|
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: Fox Chase station | Statement: [Newtown Branch, formerServiceBeyond, Fox Chase station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerServiceBeyond Context triple: [Newtown Branch, formerServiceBeyond, Fox Chase station]
-
A.
formerServicePattern
chosen
Indicates that an entity previously provided a particular service or operated under a specific service pattern, but no longer does so.
-
B.
formerCustom
Indicates that one entity was previously a customer of another entity but is no longer in that role.
-
C.
formerAccess
Indicates that an entity previously had access to another entity or resource but no longer does.
-
D.
formerBearer
Indicates that an entity previously held or carried something (such as a title, role, or object) but no longer does so.
-
E.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
- 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_69e2c4cf54248190af7b0c2d9ade9830 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9db3a9481908c7a59281e2ca994 |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:30 a.m.