Triple
T29555329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epping Ongar Railway |
E749887
|
entity |
| Predicate | sectionClosedToPassengers |
P10433
|
FINISHED |
| Object | Blake Hall–Ongar 1981 |
—
|
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: Blake Hall–Ongar 1981 | Statement: [Epping Ongar Railway, sectionClosedToPassengers, Blake Hall–Ongar 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionClosedToPassengers Context triple: [Epping Ongar Railway, sectionClosedToPassengers, Blake Hall–Ongar 1981]
-
A.
closedForPassengers
chosen
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
B.
railLineClosed
Indicates that a railway line has been officially taken out of service and is no longer operational for train traffic.
-
C.
closedForSafety
Indicates that an entity (such as a place, facility, or route) is temporarily unavailable or inaccessible due to safety concerns or hazards.
-
D.
railTrafficClosed
Indicates that rail traffic on a specific track or route is currently stopped or unavailable for use.
-
E.
closedOffFrom
Indicates that one entity is isolated, blocked, or prevented from accessing, interacting with, or being influenced by another entity.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d18c050819094ae0fdec7667e39 |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 5:15 p.m.