Triple
T3711704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spruce Street Harbor Park |
E81429
|
entity |
| Predicate | seasonal |
P31603
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Spruce Street Harbor Park, seasonal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonal Context triple: [Spruce Street Harbor Park, seasonal, true]
-
A.
season
Indicates that an entity participates in, is associated with, or occurs during a particular season or seasonal period.
-
B.
hasSeasonalNature
chosen
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
-
C.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
-
D.
seasonalReversal
Indicates a relationship where the usual seasonal pattern or effect between entities is inverted or occurs in the opposite manner from what is typically expected.
-
E.
hasSeasonalPattern
Indicates that the occurrence, intensity, or characteristics of something regularly vary according to a recurring seasonal cycle.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc58617bc8190bb712d1c90394215 |
completed | March 8, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.