Triple
T11910196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S7 stock (DLR type) |
E283372
|
entity |
| Predicate | fareSystemCompatibility |
P395
|
FINISHED |
| Object | Docklands Light Railway ticketing system |
—
|
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: Docklands Light Railway ticketing system | Statement: [S7 stock (DLR type), fareSystemCompatibility, Docklands Light Railway ticketing system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareSystemCompatibility Context triple: [S7 stock (DLR type), fareSystemCompatibility, Docklands Light Railway ticketing system]
-
A.
fareSystem
chosen
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
-
B.
hasFareControlIntegrationSince
Indicates that a fare control system has been integrated with another system or entity starting from a specific point in time.
-
C.
hasFareZoneSystem
Indicates that an entity uses or is associated with a particular fare zone system for determining travel costs or ticketing.
-
D.
fareSystemChange
Indicates a change in the rules, structure, or method by which fares are calculated, collected, or applied.
-
E.
fareTypes
Indicates the categories or kinds of fares (e.g., ticket or pricing options) that apply to a given travel or service offering.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5278eb081909a7ecfe38beeeda9 |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.