Triple
T19686459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaula |
E472722
|
entity |
| Predicate | hasPeakVisibilitySeason |
P33199
|
FINISHED |
| Object | northern 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: northern summer | Statement: [Shaula, hasPeakVisibilitySeason, northern summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakVisibilitySeason Context triple: [Shaula, hasPeakVisibilitySeason, northern summer]
-
A.
hasPeakVisitationSeason
Indicates that an entity experiences its highest or most concentrated level of visitation during a specific season or time period.
-
B.
visibleInSeason
chosen
Indicates that something can be seen or is observable during a particular season.
-
C.
isSeasonalAttraction
Indicates that an attraction is available or prominently featured only during specific seasons or times of the year.
-
D.
peakVisibility
Indicates the degree to which a peak (such as a mountain or summit) is visible from a given location or under certain conditions.
-
E.
hasSeasonalHighlight
Indicates that something features a notable or emphasized aspect during a particular season or time of year.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420c3f50819082b64b1fa4335e56 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.