Triple
T22236441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 323 |
E549604
|
entity |
| Predicate | hasDrivingCabs |
P146850
|
FINISHED |
| Object | 2 |
—
|
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 | Statement: [British Rail Class 323, hasDrivingCabs, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrivingCabs Context triple: [British Rail Class 323, hasDrivingCabs, 2]
-
A.
hasTaxiStand
Indicates that a location or facility includes or is served by a designated taxi stand area where taxis can wait for passengers.
-
B.
hasCabType
Indicates that an entity is associated with or characterized by a specific type or category of cab.
-
C.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
D.
canDrive
Indicates that one entity has the ability or permission to operate a vehicle or drive another entity.
-
E.
hasBusOperator
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12bf7b1d8819091087dcfdb2e967c |
completed | April 28, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:38 p.m.