Triple
T38268313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention Center Station |
E1021131
|
entity |
| Predicate | typicalPeakUsage |
—
|
GENERATED |
| Object | during major conventions |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPeakUsage Context triple: [Convention Center Station, typicalPeakUsage, during major conventions]
-
A.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
B.
hasPeakUse
Indicates that something reaches its highest or most intensive level of use during a particular time or condition.
-
C.
approximateUserPeak
Indicates that one value or event is an estimated or inferred maximum point associated with a particular user.
-
D.
typicalConsumption
Indicates the usual or characteristic amount or pattern in which one entity consumes or uses another.
-
E.
peakUse
chosen
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
- F. None of above.
Provenance (1 batch)
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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.