Triple
T25490317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chingam |
E638819
|
entity |
| Predicate | typicalEndGregorian |
P19627
|
FINISHED |
| Object | mid-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: mid-September | Statement: [Chingam, typicalEndGregorian, mid-September]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEndGregorian Context triple: [Chingam, typicalEndGregorian, mid-September]
-
A.
typicalEndDay
Indicates the usual or most common day on which an event, activity, or state typically concludes.
-
B.
typicalEndDate
chosen
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
C.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
D.
endEraInGregorianCalendar
Indicates that a particular era or historical period concludes on a specified date in the Gregorian calendar.
-
E.
endDateFirstUseGregorian
Indicates the calendar date, expressed in the Gregorian system, on which the first use of something ended or ceased.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 21, 2026, 2:38 p.m.