Triple
T23013833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wadhurst railway station |
E572976
|
entity |
| Predicate | typicalOffPeakFrequencyToHastings |
P150678
|
FINISHED |
| Object | 2 trains per hour |
—
|
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: 2 trains per hour | Statement: [Wadhurst railway station, typicalOffPeakFrequencyToHastings, 2 trains per hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOffPeakFrequencyToHastings Context triple: [Wadhurst railway station, typicalOffPeakFrequencyToHastings, 2 trains per hour]
-
A.
offPeakServiceFrequency_minutes
Indicates the number of minutes between successive services during off-peak periods.
-
B.
typicalOffPeakServiceTo
Indicates the usual or standard off-peak (non-peak time) service pattern that operates to a given destination.
-
C.
hasOffPeakUsage
Indicates that an entity exhibits or is associated with usage occurring during designated off-peak times rather than standard peak periods.
-
D.
typicalFrequencyWeekdayDaytime
Indicates the usual or most common frequency with which something occurs during daytime hours on weekdays.
-
E.
hasPeakHourFrequency
Indicates how often a service or event occurs during designated peak hours.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e300008190bb12c6388a8b3280 |
completed | April 29, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:51 p.m.