Triple
T21132643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London St Pancras – Derby |
E520725
|
entity |
| Predicate | onTimePerformanceMetric |
P40595
|
FINISHED |
| Object | Public Performance Measure |
—
|
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: Public Performance Measure | Statement: [London St Pancras – Derby, onTimePerformanceMetric, Public Performance Measure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onTimePerformanceMetric Context triple: [London St Pancras – Derby, onTimePerformanceMetric, Public Performance Measure]
-
A.
performanceTime
Indicates the specific time or time interval at which a performance or event takes place.
-
B.
performanceMeasurement
chosen
Indicates the act of assessing, quantifying, or evaluating how well an entity, process, or system performs against defined criteria or objectives.
-
C.
hasTypicalPerformanceDuration
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
D.
performedMeasurement
Indicates that an entity has carried out a specific measurement activity on another entity or phenomenon.
-
E.
performsAt
Indicates that an entity carries out or presents a performance at a specific location, venue, or event.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723574b1481909fe9bebc83f1f3ce |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.