Triple
T24996082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maida Hill Tunnel |
E625570
|
entity |
| Predicate | connectsSectionsOf |
P164769
|
FINISHED |
| Object | Regent’s Canal |
—
|
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: Regent’s Canal | Statement: [Maida Hill Tunnel, connectsSectionsOf, Regent’s Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsSectionsOf Context triple: [Maida Hill Tunnel, connectsSectionsOf, Regent’s Canal]
-
A.
connectsIslandSection
Indicates a relationship where one entity serves as a link or passage that joins or bridges separate sections of an island.
-
B.
connectsPartOf
Indicates a relationship where one entity serves to link or join a component to the larger whole of which that component is a part.
-
C.
connectsPreviouslySeparateSystems
Indicates that an entity establishes a link or integration between systems that were previously independent or isolated from one another.
-
D.
connectsProvincesAlong
Indicates a relationship where something serves as a link or route joining multiple provinces along a specified path or alignment.
-
E.
linkedSector
Indicates that one sector is associated or connected to another sector in a meaningful or relevant way.
- F. None of above. chosen
Provenance (4 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 18, 2026, 6:04 a.m.