Triple
T8910726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Downs Tunnel |
E212173
|
entity |
| Predicate | maximumLineSpeed |
P2096
|
FINISHED |
| Object | up to 300 km/h |
—
|
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: up to 300 km/h | Statement: [North Downs Tunnel, maximumLineSpeed, up to 300 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumLineSpeed Context triple: [North Downs Tunnel, maximumLineSpeed, up to 300 km/h]
-
A.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
maximumBitrate
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
C.
originalLineSpeed
Indicates the speed at which something initially moves or operates before any changes or adjustments are made.
-
D.
maxCableLength
Indicates the maximum allowable length of a cable in the specified context or configuration.
-
E.
maxDataTransferMode
Indicates the data transfer mode in which the maximum possible data throughput is achieved between entities.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6523b9348190a7cefac9e73e2004 |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.