Triple
T8730070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nehase |
E207231
|
entity |
| Predicate | typicalGregorianEnd |
P19627
|
FINISHED |
| Object | September |
—
|
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 | Statement: [Nehase, typicalGregorianEnd, September]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGregorianEnd Context triple: [Nehase, typicalGregorianEnd, September]
-
A.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
B.
typicalEndDate
chosen
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
C.
typicalDSTEndMonth
Indicates the month in which daylight saving time typically ends for a given region or system.
-
D.
typicalEndSeason
Indicates the season in which something (such as an activity, event, or condition) usually or characteristically comes to an end.
-
E.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d26d280819085e15d4917c2b9a5 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:37 p.m.