Triple
T774034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Songkran |
E16347
|
entity |
| Predicate | typicalEndDate |
P19627
|
FINISHED |
| Object | April 15 |
—
|
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: April 15 | Statement: [Songkran, typicalEndDate, April 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEndDate Context triple: [Songkran, typicalEndDate, April 15]
-
A.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
B.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
C.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
D.
typicalEndSeason
Indicates the season in which something (such as an activity, event, or condition) usually or characteristically comes to an end.
-
E.
typicalDates
Indicates the usual or standard dates during which something typically occurs, is valid, or is scheduled.
- F. None of above. chosen
Provenance (4 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a74da7648190adfad56717d564df |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a50a443481909ae3662764ee69a4 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a74c81bc81909f4ac9c1677b09c2 |
completed | March 1, 2026, 8:53 p.m. |
Created at: March 1, 2026, 7:37 p.m.