Triple
T15988456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahmedabad BRTS |
E387758
|
entity |
| Predicate | offPeakOperation |
P24204
|
FINISHED |
| Object | reduced frequency service |
—
|
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: reduced frequency service | Statement: [Ahmedabad BRTS, offPeakOperation, reduced frequency service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offPeakOperation Context triple: [Ahmedabad BRTS, offPeakOperation, reduced frequency service]
-
A.
offPeakServicePattern
chosen
Indicates the service pattern or schedule that applies during off-peak (non-rush-hour) times.
-
B.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
-
C.
offPeakServiceFrequency_minutes
Indicates the number of minutes between successive services during off-peak periods.
-
D.
inOperationDuring
Indicates that an entity is actively functioning or in use throughout a specified time period or event.
-
E.
isOnPeak
Indicates that one entity is located at, or positioned on, the highest point or summit of another entity.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4e871c819082d7b1c1eaf5b4fe |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.