Triple
T29468692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jāņi |
E747449
|
entity |
| Predicate | hasOppositeSeasonalFestival |
P61951
|
FINISHED |
| Object | Ziemassvētki |
—
|
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: Ziemassvētki | Statement: [Jāņi, hasOppositeSeasonalFestival, Ziemassvētki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOppositeSeasonalFestival Context triple: [Jāņi, hasOppositeSeasonalFestival, Ziemassvētki]
-
A.
hasSeasonalCounterpart
chosen
Indicates that one entity corresponds to another entity that appears or is relevant in a different season as its counterpart.
-
B.
hasOppositeSeasonTime
Indicates that two locations experience opposite seasons at the same time of year (e.g., when it is summer in one, it is winter in the other).
-
C.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
-
D.
famousSeasonalEvent
Indicates a recurring event that is widely recognized or celebrated during a particular season.
-
E.
hasFestivalPeriod
Indicates that there is a specific time period during which a festival or celebratory event takes place.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 3:55 p.m.