Triple
T30223474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCRTA |
E768410
|
entity |
| Predicate | hasParatransitServiceName |
P5908
|
FINISHED |
| Object | RTA Paratransit |
—
|
NE NERFINISHED |
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: RTA Paratransit | Statement: [GCRTA, hasParatransitServiceName, RTA Paratransit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParatransitServiceName Context triple: [GCRTA, hasParatransitServiceName, RTA Paratransit]
-
A.
paratransitSystemName
chosen
Indicates the name assigned to a specific paratransit transportation system or service.
-
B.
hasTransitServiceType
Indicates that a transit service is associated with a specific type or category of service (e.g., bus, rail, express).
-
C.
paratransitEligibility
Indicates that an individual meets the criteria to use specialized transportation services (paratransit) provided as an alternative to standard public transit.
-
D.
hasPublicTransitServiceLevel
Indicates the level or quality of public transit service provided to or available at a given location or entity.
-
E.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 29, 2026, 7:35 p.m.