Triple
T30223475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCRTA |
E768410
|
entity |
| Predicate | hasBusRapidTransitBrand |
P142506
|
FINISHED |
| Object | HealthLine |
—
|
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: HealthLine | Statement: [GCRTA, hasBusRapidTransitBrand, HealthLine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusRapidTransitBrand Context triple: [GCRTA, hasBusRapidTransitBrand, HealthLine]
-
A.
publicTransportBrand
chosen
Indicates that a public transport service, line, or vehicle operates under or is associated with a specific brand or branding entity.
-
B.
hasBusRapidTransitFeatures
Indicates that a transportation route or corridor includes design or operational elements characteristic of bus rapid transit systems.
-
C.
hasBRTLine
Indicates that a bus rapid transit (BRT) line is present, operates on, or serves the referenced entity.
-
D.
commuterRailBrand
Indicates that a commuter rail service operates under or is associated with a specific brand or branding identity.
-
E.
isPublicTransportBackboneOf
Indicates that one transport system serves as the primary structural and functional core of a region’s overall public transportation network.
- 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_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 29, 2026, 7:35 p.m.