Triple
T514682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandwich Boardwalk |
E10679
|
entity |
| Predicate | hasSeasonalUse |
P8056
|
FINISHED |
| Object | year-round |
—
|
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: year-round | Statement: [Sandwich Boardwalk, hasSeasonalUse, year-round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonalUse Context triple: [Sandwich Boardwalk, hasSeasonalUse, year-round]
-
A.
usedInSeason
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
B.
isUsedAllYear
chosen
Indicates that something is utilized or remains in active use throughout the entire year, without being limited to a particular season or period.
-
C.
hasSeasonalPattern
Indicates that the occurrence, intensity, or characteristics of something regularly vary according to a recurring seasonal cycle.
-
D.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
E.
hasSeasonalDecorations
Indicates that an entity is adorned with decorations that are specific to a particular season or holiday 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f232fa688190b08a2fe3f22c7a6e |
completed | Feb. 28, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69a2f013c05481909e6dc87e7b20ebd8 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.