Triple
T18681391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grizzly Peak Boulevard scenic overlooks |
E456740
|
entity |
| Predicate | timeOfHighestUse |
P34607
|
FINISHED |
| Object | evenings |
—
|
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: evenings | Statement: [Grizzly Peak Boulevard scenic overlooks, timeOfHighestUse, evenings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfHighestUse Context triple: [Grizzly Peak Boulevard scenic overlooks, timeOfHighestUse, evenings]
-
A.
usagePeak
chosen
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
B.
timeOfPeakSize
Indicates the specific time at which something reaches its maximum size or extent.
-
C.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
-
D.
approximateUserPeak
Indicates that one value or event is an estimated or inferred maximum point associated with a particular user.
-
E.
hasTimeOfHighActivity
Indicates that an entity experiences its peak or most intense level of activity during a specified time period.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2840548190ababe1cc603b4784 |
completed | April 19, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.