Triple
T34313655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTA bus 78 Montrose |
E880518
|
entity |
| Predicate | hasServiceProviderType |
P86906
|
FINISHED |
| Object | public transit agency |
—
|
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: public transit agency | Statement: [CTA bus 78 Montrose, hasServiceProviderType, public transit agency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceProviderType Context triple: [CTA bus 78 Montrose, hasServiceProviderType, public transit agency]
-
A.
hasServiceProvider
Indicates that an entity is associated with or supported by a specific service provider.
-
B.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
C.
serviceProviderType
chosen
Indicates the category or kind of service provider associated with an entity or transaction.
-
D.
hasTypeOfSupport
Indicates that one entity provides or is associated with a particular kind or category of support in relation to another entity.
-
E.
hasPeakServiceType
Indicates that an entity is associated with a specific type or category of service provided during peak periods.
- 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
Created at: May 1, 2026, 1:57 a.m.