Triple
T26159073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corwin House |
E660054
|
entity |
| Predicate | hasTourSeason |
P1014
|
FINISHED |
| Object | primarily spring through fall |
—
|
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: primarily spring through fall | Statement: [Corwin House, hasTourSeason, primarily spring through fall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourSeason Context triple: [Corwin House, hasTourSeason, primarily spring through fall]
-
A.
hasSeason
chosen
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
B.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
-
C.
hasSeasonalParticipationIn
Indicates that an entity takes part in or is involved with another entity only during specific seasons or recurring seasonal periods.
-
D.
hasSeasonalRound
Indicates a recurring, seasonally patterned cycle of movements, activities, or resource use associated with an entity over the course of a year.
-
E.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 26, 2026, 8:29 p.m.