Triple
T3962572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | June |
E85938
|
entity |
| Predicate | astronomicalEvent |
P34853
|
FINISHED |
| Object | June solstice |
—
|
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 | Statement: [June, astronomicalEvent, June solstice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: astronomicalEvent Context triple: [June, astronomicalEvent, June solstice]
-
A.
containsAstronomicalEvent
chosen
Indicates that a location, region, or time period includes or encompasses a specific astronomical event within its bounds or duration.
-
B.
astronomicalType
Indicates the classification relationship that specifies what kind of astronomical object or phenomenon something is (e.g., star, galaxy, planet).
-
C.
astronomicalAchievement
Indicates an entity has accomplished a notable or significant feat in the field of astronomy or space exploration.
-
D.
DeAstronomicaIs
Indicates that something is identified as or classified as "De Astronomica" (e.g., belonging to or being the work/text known as De Astronomica).
-
E.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:31 p.m.