Triple
T22285381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xpress commuter bus service |
E550846
|
entity |
| Predicate | typicalRiderType |
P84828
|
FINISHED |
| Object | commuters |
—
|
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: commuters | Statement: [Xpress commuter bus service, typicalRiderType, commuters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRiderType Context triple: [Xpress commuter bus service, typicalRiderType, commuters]
-
A.
typicalRiderAgeRange
Indicates the usual or most common age range of people who ride or use something.
-
B.
typicalRiderOrientation
Indicates the usual or standard physical position or alignment a rider maintains relative to what they are riding.
-
C.
intendedRiderExperience
Indicates the type or quality of experience that is planned or designed for a rider in the context of a ride or transportation service.
-
D.
typicalRiderEmotion
Indicates the characteristic or commonly experienced emotion that a rider typically feels in the context of a particular riding situation or activity.
-
E.
riderType
chosen
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15606948c81909ebaa5ea106d2b7a |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.