Triple
T3052778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | September |
E60409
|
entity |
| Predicate | typicalEquinoxDateRange |
P18044
|
FINISHED |
| Object | September 22–24 |
—
|
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: September 22–24 | Statement: [September, typicalEquinoxDateRange, September 22–24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEquinoxDateRange Context triple: [September, typicalEquinoxDateRange, September 22–24]
-
A.
eclipticLongitudeRange
Indicates that an entity’s ecliptic longitude lies within a specified angular range along the ecliptic.
-
B.
solarAlignmentDates
Indicates the specific dates on which an object, structure, or location is aligned in a significant way with the position of the Sun (e.g., sunrise, sunset, solstices, or equinoxes).
-
C.
endDateSidereal
Indicates the date and time, measured in sidereal rather than solar terms, at which a specified event, state, or interval comes to an end.
-
D.
typicalDates
chosen
Indicates the usual or standard dates during which something typically occurs, is valid, or is scheduled.
-
E.
typicalSeasonTiming
Indicates the usual time period or season during which something normally occurs or is expected to take 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9bf3c52c8190bbe8e5cb98c21715 |
completed | March 8, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.