Triple
T15980669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STM paratransit services |
E387561
|
entity |
| Predicate | pickupPolicy |
P61825
|
FINISHED |
| Object | door-to-door pickup and drop-off |
—
|
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: door-to-door pickup and drop-off | Statement: [STM paratransit services, pickupPolicy, door-to-door pickup and drop-off]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pickupPolicy Context triple: [STM paratransit services, pickupPolicy, door-to-door pickup and drop-off]
-
A.
pickupOption
Indicates that one entity offers or selects a method or arrangement for collecting or retrieving another entity (such as goods, items, or services).
-
B.
pickupConfiguration
Indicates the specific arrangement or setup in which one entity is collected, retrieved, or picked up by another.
-
C.
pickupType
chosen
Indicates the manner or method by which an item or person is collected or retrieved (e.g., in-store pickup, curbside, scheduled pickup).
-
D.
hasPickup
Indicates that one entity is assigned or associated with a specific pickup location, time, or arrangement for collection.
-
E.
laterPickupSelector
Indicates a choice or mechanism for selecting a pickup time that occurs later than an initial or default option.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.