Triple
T30733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Hemisphere |
E612
|
entity |
| Predicate | experiencesEvent |
P1664
|
FINISHED |
| Object | June solstice around June 20–21 |
—
|
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: June solstice around June 20–21 | Statement: [Northern Hemisphere, experiencesEvent, June solstice around June 20–21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencesEvent Context triple: [Northern Hemisphere, experiencesEvent, June solstice around June 20–21]
-
A.
participatedInEvent
Indicates that an entity took part in or was actively involved in a specific event.
-
B.
event
chosen
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
C.
hostsEvent
Indicates that an entity organizes and provides the venue or setting for an event to take place.
-
D.
activity
Indicates that an entity is engaged in or performing a particular action, behavior, or process.
-
E.
oversawEvent
Indicates that an entity had supervisory or managerial responsibility for the planning, execution, or overall conduct of an event.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490d80a0819083bf604c1229e903 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a2486eb01881909241540dda28e1ff |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.