Triple
T25711041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worcester Union Station |
E644729
|
entity |
| Predicate | dateReopened |
P34772
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Worcester Union Station, dateReopened, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateReopened Context triple: [Worcester Union Station, dateReopened, 2000]
-
A.
dateReRaised
Indicates that a previously raised issue, request, or event has been brought up again on a later date.
-
B.
reopenedAfter
chosen
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
-
C.
reopenedFor
Indicates that an entity, previously closed or inactive, has been opened again to allow access, use, or operation for another entity or purpose.
-
D.
reopenedBy
Indicates that a previously closed or resolved item, case, or process has been opened again by a specific agent or entity.
-
E.
recoveryDate
Indicates the date on which a recovery process or restoration of a prior state is completed or officially recorded.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc157d9c819096b30f09438e351a |
completed | May 2, 2026, 1:28 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 9:13 p.m.