Triple
T31795416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Transit Authority |
E811581
|
entity |
| Predicate | statusOfBusOperations |
P9581
|
FINISHED |
| Object | privatised |
—
|
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: privatised | Statement: [State Transit Authority, statusOfBusOperations, privatised]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfBusOperations Context triple: [State Transit Authority, statusOfBusOperations, privatised]
-
A.
operatingStatus
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
B.
railStatus
Indicates the current operational condition or state of a rail-related entity (such as a track, line, or service) within the system.
-
C.
publicTransportStatus
chosen
Indicates the current operational condition or availability of a public transportation service or route.
-
D.
statusOfTrain7
Indicates the current operational status or condition of train number 7 in relation to its schedule or service.
-
E.
followingTrainStatus
Indicates that one entity is tracking or monitoring the current operational status or progress of a train.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: April 30, 2026, 11:40 p.m.