Triple
T10279357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 8th Street (Oakland) |
E241052
|
entity |
| Predicate | timeActivityPattern |
P70162
|
FINISHED |
| Object | busiest during daytime and early evening hours |
—
|
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: busiest during daytime and early evening hours | Statement: [8th Street (Oakland), timeActivityPattern, busiest during daytime and early evening hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeActivityPattern Context triple: [8th Street (Oakland), timeActivityPattern, busiest during daytime and early evening hours]
-
A.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
B.
activityPeakPeriod
chosen
Indicates the time period during which an activity reaches its highest level or intensity.
-
C.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
D.
travelPattern
Indicates the typical routes, frequencies, and behaviors associated with how an entity moves or travels between locations.
-
E.
peakActivity
Indicates that an entity is at its highest or most intense level of activity within a given period or context.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:38 a.m.