Triple
T2722416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asalha Puja |
E60110
|
entity |
| Predicate | legalStatusInThailand |
P39644
|
FINISHED |
| Object | public holiday |
—
|
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: public holiday | Statement: [Asalha Puja, legalStatusInThailand, public holiday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInThailand Context triple: [Asalha Puja, legalStatusInThailand, public holiday]
-
A.
legalStatusInManyCountries
Indicates that the subject has a particular legal classification or standing that is recognized across numerous countries.
-
B.
legalStatusVariesBy
chosen
Indicates that the legal status of something differs depending on a specified jurisdiction, context, or set of conditions.
-
C.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
-
D.
legalStatusAccordingToUkraine
Indicates the legal status or classification of an entity as defined specifically by the laws and regulations of Ukraine.
-
E.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdab2f36c8190aa0b452e57525fe0 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.