Triple
T6323104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBTA paratransit service |
E141791
|
entity |
| Predicate | serviceConstraint |
P99
|
FINISHED |
| Object | advance scheduling required |
—
|
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: advance scheduling required | Statement: [MBTA paratransit service, serviceConstraint, advance scheduling required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceConstraint Context triple: [MBTA paratransit service, serviceConstraint, advance scheduling required]
-
A.
typicalServiceRequirement
Indicates that a certain condition, resource, or specification is normally needed or expected for a service to be properly provided or operated.
-
B.
serviceCommitmentRequired
Indicates that entering into or receiving something involves an obligation to perform a specified period or type of service.
-
C.
serviceUserRequirement
Indicates that a user has a specific requirement or need that a service is expected to fulfill.
-
D.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
E.
serviceCharacterization
Indicates how a service is defined, described, or classified in terms of its properties, behavior, or role.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e38f1c81909c7e90b520602bae |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.