Triple
T25887875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinhagad Road |
E652240
|
entity |
| Predicate | hasCityBusServiceOperator |
P14541
|
FINISHED |
| Object | PMPML |
—
|
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: PMPML | Statement: [Sinhagad Road, hasCityBusServiceOperator, PMPML]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityBusServiceOperator Context triple: [Sinhagad Road, hasCityBusServiceOperator, PMPML]
-
A.
hasBusOperator
chosen
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
-
B.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
C.
hasPublicTransportAgency
Indicates that a place or transport system is served, managed, or overseen by a specific public transportation agency.
-
D.
publicTransportOperatorFor
Indicates that one entity operates or manages public transportation services for another entity or area.
-
E.
operatesInterurbanBusServices
Indicates that an entity runs or manages bus transportation services operating between different towns or cities within a region.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 22, 2026, 8:18 a.m.