Triple
T1258019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburgh commuter rail network |
E12435
|
entity |
| Predicate | peakUsage |
P10921
|
FINISHED |
| Object | weekday peak hours |
—
|
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: weekday peak hours | Statement: [Edinburgh commuter rail network, peakUsage, weekday peak hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakUsage Context triple: [Edinburgh commuter rail network, peakUsage, weekday peak hours]
-
A.
peakStatus
Indicates the condition or phase of something at its highest or most intense point in its progression or lifecycle.
-
B.
peakActivity
chosen
Indicates that an entity is at its highest or most intense level of activity within a given period or context.
-
C.
peakDayAttendance
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
D.
fanUsage
Indicates that an entity uses, operates, or relies on a fan (e.g., for cooling, ventilation, or air circulation) in relation to another entity or context.
-
E.
trackUsage
Indicates that one entity monitors and records how another entity or resource is being used over time.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfaa2b508190a3f61c67b3fa3ad4 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.