Triple
T27136448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skeleton Point |
E681699
|
entity |
| Predicate | lessIdealSeason |
P90952
|
FINISHED |
| Object | mid-summer due to heat |
—
|
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: mid-summer due to heat | Statement: [Skeleton Point, lessIdealSeason, mid-summer due to heat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lessIdealSeason Context triple: [Skeleton Point, lessIdealSeason, mid-summer due to heat]
-
A.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
-
B.
lowSeason
chosen
Indicates that the relationship or activity occurs during a period of reduced demand, traffic, or activity (the off-peak or less busy season).
-
C.
usualSeason
Indicates the season during which something typically or most commonly occurs.
-
D.
nonTraditionalSeason
Indicates that an event, activity, or occurrence takes place outside the customary or standard season in which it is typically expected.
-
E.
hasEasiestSeason
Indicates that one season is considered the least difficult or most favorable compared to other seasons for a given activity, condition, 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6247b68108190a39e59f865e751a0 |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:07 a.m.