Triple
T3387982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacramento Regional Transit |
E71347
|
entity |
| Predicate | lightRailServiceBegan |
P10389
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Sacramento Regional Transit, lightRailServiceBegan, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightRailServiceBegan Context triple: [Sacramento Regional Transit, lightRailServiceBegan, 1987]
-
A.
hasLightRailSystem
Indicates that a place possesses and operates a light rail transit system.
-
B.
rapidTransitSystem
Indicates a transportation relationship where people or goods are moved via a high-capacity, high-frequency public transit system designed for rapid travel over urban or regional routes.
-
C.
metroLineInaugurated
chosen
Indicates that a metro line was officially opened and began operation on a specific date or during a specific event.
-
D.
Purple Line Express
Indicates a transportation service or route designated as the "Purple Line" that operates with express (limited-stop) service between locations.
-
E.
hasTramway
Indicates that a location or area is served by, contains, or is connected to a tramway system.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb665c6008190b33994ef20f5bd61 |
completed | March 8, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69ada43615f08190ac2275020d157983 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.