Triple
T29319997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maasi |
E743489
|
entity |
| Predicate | seasonalPosition |
P130484
|
FINISHED |
| Object | late winter |
—
|
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: late winter | Statement: [Maasi, seasonalPosition, late winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalPosition Context triple: [Maasi, seasonalPosition, late winter]
-
A.
hasSeasonalPositionSouthernHemisphere
Indicates that an entity’s seasonal position or phase is defined specifically with respect to conditions in the Southern Hemisphere.
-
B.
typicalPositionInNorthernHemisphereSeasonCycle
Indicates the usual or characteristic point within the annual sequence of seasons in the Northern Hemisphere at which something occurs or is situated.
-
C.
seasonalOrder
chosen
Indicates the temporal ordering of events or states according to their position within a recurring seasonal cycle.
-
D.
seasonalDirection
Indicates the direction or trend of change in a phenomenon as it varies across different seasons.
-
E.
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.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 28, 2026, 1:22 p.m.