Triple
T7696643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank of Thailand Act B.E. 2485 (1942) |
E174386
|
entity |
| Predicate | BuddhistEraYear |
P78338
|
FINISHED |
| Object | 2485 |
—
|
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: 2485 | Statement: [Bank of Thailand Act B.E. 2485 (1942), BuddhistEraYear, 2485]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BuddhistEraYear Context triple: [Bank of Thailand Act B.E. 2485 (1942), BuddhistEraYear, 2485]
-
A.
timeInChineseEraSystem
Indicates that a temporal reference is expressed using a specific Chinese era-based calendrical system (such as reign titles or traditional era names).
-
B.
hasJapaneseEraBirthYear
Indicates that an entity’s birth year is specified according to the Japanese era (gengō) calendar system.
-
C.
positionInEra
Indicates the temporal placement or role of something within a specific historical or chronological era.
-
D.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
E.
birthYearHijri
Indicates the year of an entity’s birth expressed in the Hijri (Islamic) calendar.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7040091608190a9e46ecfb2ff0bca |
completed | March 27, 2026, 10:26 p.m. |
Created at: March 27, 2026, 4:03 p.m.