Triple
T24973882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transportation in Montgomery County, Maryland |
E624963
|
entity |
| Predicate | localBusOperator |
P14541
|
FINISHED |
| Object | Ride On |
—
|
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: Ride On | Statement: [Transportation in Montgomery County, Maryland, localBusOperator, Ride On]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localBusOperator Context triple: [Transportation in Montgomery County, Maryland, localBusOperator, Ride On]
-
A.
publicTransportOperatorFor
Indicates that one entity operates or manages public transportation services for another entity or area.
-
B.
hasBusOperator
chosen
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
-
C.
tramOperator
Indicates that one entity operates, manages, or runs tram services for another entity or area.
-
D.
cityTransportOperatorAffected
Indicates that a city transport operator is impacted or influenced by a particular event, condition, or circumstance.
-
E.
transportOperator
Indicates that an entity is responsible for operating or managing the transportation of people or goods between locations.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490283c481908c18246dc7125eec |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:01 a.m.