Triple
T38188784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Manchester |
E1005393
|
entity |
| Predicate | hasPlannedHighSpeedRailProject |
P66623
|
FINISHED |
| Object | HS2 Phase 2 |
—
|
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: HS2 Phase 2 | Statement: [London–Manchester, hasPlannedHighSpeedRailProject, HS2 Phase 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedHighSpeedRailProject Context triple: [London–Manchester, hasPlannedHighSpeedRailProject, HS2 Phase 2]
-
A.
hasHighSpeedRailProposal
chosen
Indicates that there exists a proposed plan or project to develop or implement a high-speed rail system involving the related entities.
-
B.
hasHighSpeedLine
Indicates that there exists a high-speed rail line connection between the related entities.
-
C.
firstHighSpeedRailIn
Indicates that a given rail system is the earliest high-speed rail established within a specified region or country.
-
D.
hasHighSpeedRailStation
Indicates that a location is served by a high-speed rail station where high-speed trains regularly stop.
-
E.
hasExpresswayProject
Indicates that an entity is associated with or involved in an expressway-related development or construction project.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:29 p.m.