Triple
T24994496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cranbourne–Pakenham corridor |
E625530
|
entity |
| Predicate | peakDemandLevel |
P35920
|
FINISHED |
| Object | very high passenger volumes |
—
|
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: very high passenger volumes | Statement: [Cranbourne–Pakenham corridor, peakDemandLevel, very high passenger volumes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakDemandLevel Context triple: [Cranbourne–Pakenham corridor, peakDemandLevel, very high passenger volumes]
-
A.
peakDemandUnit
Indicates the unit of measurement used to express the peak level of demand in a given context.
-
B.
peakDay
Indicates the specific day on which a quantity, activity, or effect reaches its maximum level within a given period.
-
C.
peakUse
chosen
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
D.
peakRating
Indicates the highest rating value that has been achieved or recorded for an entity over a given period or context.
-
E.
peakLoadContribution
Indicates the extent to which an entity’s usage or demand contributes to the maximum (peak) load within a system or 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44a48bb8c819087ddf6df8c446489 |
completed | May 1, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:04 a.m.