Triple
T31795402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Transit Authority |
E811581
|
entity |
| Predicate | busOperationsPrivatised |
P172310
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [State Transit Authority, busOperationsPrivatised, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busOperationsPrivatised Context triple: [State Transit Authority, busOperationsPrivatised, yes]
-
A.
railPrivatisationContext
Indicates the relationship in which an event, statement, or policy is situated within the broader circumstances or framework of rail privatisation.
-
B.
privatizedOn
Indicates the date or point in time when an entity transitioned from public or state ownership/control to private ownership/control.
-
C.
operatedPassengerServices
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
D.
formerTransportAuthority
Indicates that an entity previously served as a transport authority for another entity but no longer holds that role.
-
E.
publicTransportOperatorFor
Indicates that one entity operates or manages public transportation services for another entity or area.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac1d488c8190afbf41c0589d2efe |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aac95c1481909fff33702d0a6c37 |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:40 p.m.