Triple
T2572446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarborough RT |
E57694
|
entity |
| Predicate | serviceSuspensionDate |
P38380
|
FINISHED |
| Object | 2023-07-24 |
—
|
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: 2023-07-24 | Statement: [Scarborough RT, serviceSuspensionDate, 2023-07-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceSuspensionDate Context triple: [Scarborough RT, serviceSuspensionDate, 2023-07-24]
-
A.
suspensionDate
chosen
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
-
B.
suspendedBy
Indicates that one entity has temporarily halted, removed, or placed another entity in an inactive or pending state, typically as an enforcement or administrative action.
-
C.
charterRevocationDate
Indicates the date on which a charter was officially revoked or terminated.
-
D.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
-
E.
decommissioningStartDate
Indicates the date on which the process of taking an asset or system out of active service is initiated.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3853c848190970e8a2da16d726d |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0ce4dcc8190b17a65abf9bd1bb0 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.