Triple
T22004716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Joaquins Thruway Motorcoach |
E543420
|
entity |
| Predicate | serviceIntegration |
P16507
|
FINISHED |
| Object | coordinated schedules with San Joaquins rail |
—
|
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: coordinated schedules with San Joaquins rail | Statement: [San Joaquins Thruway Motorcoach, serviceIntegration, coordinated schedules with San Joaquins rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceIntegration Context triple: [San Joaquins Thruway Motorcoach, serviceIntegration, coordinated schedules with San Joaquins rail]
-
A.
integratesService
chosen
Indicates that one entity connects with and enables the functionality of another service so they work together as a unified system.
-
B.
typeOfIntegration
Indicates the specific kind or category of integration that exists or is applied between systems, components, or processes.
-
C.
integrationFeature
Indicates that one entity provides a capability or component specifically intended to enable or support integration with another system, service, or component.
-
D.
integrationProperty
Indicates a relationship where one entity serves as a property, parameter, or configuration aspect governing how another entity is integrated or combined with systems, components, or processes.
-
E.
integrationProcess
Indicates the process or workflow through which separate components, systems, or functions are combined and coordinated to operate as a unified whole.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1276d81e4819083a40e51249e7fd7 |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:20 p.m.