Triple
T30778448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snaresbrook tube station |
E783742
|
entity |
| Predicate | hasNationalRailHistory |
P28401
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Snaresbrook tube station, hasNationalRailHistory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNationalRailHistory Context triple: [Snaresbrook tube station, hasNationalRailHistory, yes]
-
A.
hasNationalRailCategory
Indicates that an entity is assigned a specific classification or category within a national rail system.
-
B.
hasNationalRailService
Indicates that a place or facility is served by a country's national rail transportation network.
-
C.
railwayHeritageFrom
Indicates that something derives its historical or cultural significance from a particular railway or railway-related source.
-
D.
hasRailroadHistory
chosen
Indicates that an entity is associated with, involved in, or notable for historical events, operations, or developments related to railroads.
-
E.
hasRailroadHistoryWith
Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 29, 2026, 8:41 p.m.