Triple
T24219779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HBY |
E601414
|
entity |
| Predicate | locatedInBoroughOfStationIdentified |
P56654
|
FINISHED |
| Object | London Borough of Islington |
—
|
NE NERFINISHED |
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: London Borough of Islington | Statement: [HBY, locatedInBoroughOfStationIdentified, London Borough of Islington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBoroughOfStationIdentified Context triple: [HBY, locatedInBoroughOfStationIdentified, London Borough of Islington]
-
A.
stationBorough
chosen
Indicates the borough or administrative district in which a station is located.
-
B.
identifiesStationWithinLine
Indicates that a specific station is recognized as belonging to, or located within, a particular transit line.
-
C.
servedByLIRRStation
Indicates that a location or facility is provided rail service by a Long Island Rail Road (LIRR) station.
-
D.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
E.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820cdd3c8190998d6d901224c09f |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:59 p.m.