Triple
T16466915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamaqua, Pennsylvania |
E399956
|
entity |
| Predicate | railroadStationStatus |
P41715
|
FINISHED |
| Object | restored |
—
|
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: restored | Statement: [Tamaqua, Pennsylvania, railroadStationStatus, restored]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadStationStatus Context triple: [Tamaqua, Pennsylvania, railroadStationStatus, restored]
-
A.
railStatus
chosen
Indicates the current operational condition or state of a rail-related entity (such as a track, line, or service) within the system.
-
B.
railwayStationOnLine
Indicates that a particular railway station is located on and served by a specified railway line.
-
C.
followingTrainStatus
Indicates that one entity is tracking or monitoring the current operational status or progress of a train.
-
D.
railTerminus
Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
-
E.
railwayTraffic
Indicates the presence, flow, or management of train movements along railway lines between locations.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dcd707081908fb7ca91a8c09e0a |
completed | April 18, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:11 a.m.