Triple
T24297108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henbury Line |
E605990
|
entity |
| Predicate | passengerServicePattern |
P155461
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [Henbury Line, passengerServicePattern, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerServicePattern Context triple: [Henbury Line, passengerServicePattern, limited]
-
A.
formerPassengerService
Indicates that an entity previously provided passenger transportation services but no longer does so.
-
B.
passengerSystem
Indicates a relationship where an entity functions as or belongs to a passenger-related system (such as a transport or service system designed for passengers).
-
C.
openedAsPassengerService
Indicates that a transportation facility or route began operating specifically for carrying passengers.
-
D.
passengerConfiguration
Indicates how passengers are arranged, seated, or distributed within a vehicle or transport setting.
-
E.
majorPassengerService
Indicates that a transportation facility or route provides primary or significant passenger service as one of its main functions.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f2915ada688190aa9c4bdaa2f1617f |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:09 a.m.