Triple
T27247557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenel station |
E687388
|
entity |
| Predicate | closedForRegularService |
P56011
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [Avenel station, closedForRegularService, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedForRegularService Context triple: [Avenel station, closedForRegularService, 1985]
-
A.
closedCityDuring
Indicates that a city is not accessible or operational during a specified time period or interval.
-
B.
closedFor
chosen
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
C.
closingTime
Indicates the specific time at which a place, service, or activity stops operating or becomes unavailable.
-
D.
closedAsRegularAttraction
Indicates that an attraction has been permanently closed in its capacity as a regular, ongoing visitor destination rather than as a temporary or special event.
-
E.
temporarilyClosedFrom
Indicates that an entity is not accessible or operating for a specific, limited time period starting from a given point.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 10:42 a.m.