Triple
T3303107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay View Historic District (adjacent community) |
E69381
|
entity |
| Predicate | seasonalOccupation |
P1166
|
FINISHED |
| Object | summer |
—
|
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: summer | Statement: [Bay View Historic District (adjacent community), seasonalOccupation, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalOccupation Context triple: [Bay View Historic District (adjacent community), seasonalOccupation, summer]
-
A.
season
chosen
Indicates that an entity participates in, is associated with, or occurs during a particular season or seasonal period.
-
B.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
-
C.
peakEmployment
Indicates that an entity has reached its highest level of employment or workforce size during a specified period.
-
D.
hasSeasonalNature
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
-
E.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0c662308190aad8b2a93e1c8a5c |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.