Triple
T92376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEPTA Subway–Surface Trolley Lines |
E1855
|
entity |
| Predicate | openingPeriod |
P617
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [SEPTA Subway–Surface Trolley Lines, openingPeriod, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingPeriod Context triple: [SEPTA Subway–Surface Trolley Lines, openingPeriod, early 20th century]
-
A.
openedForUse
Indicates that something has been made accessible and available for its intended operation or use.
-
B.
opened
Indicates that one entity caused another entity (such as an object, container, or passage) to change from a closed or inaccessible state to an open or accessible state.
-
C.
openedIn
chosen
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
D.
isOpenTo
Indicates that one entity is receptive, willing, or available to consider, accept, or engage with another entity or proposal.
-
E.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
- 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_69a24d1a97dc819094e6c021fe9b05a7 |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a2512ef600819084d3c627f0d534f4 |
completed | Feb. 28, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69a24eb9a5ac8190b1d1300e8c4e3606 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:07 a.m.