Triple
T23756257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mu Ko Similan National Park |
E587123
|
entity |
| Predicate | closedMonthsApprox |
P12551
|
FINISHED |
| Object | mid-May to mid-October |
—
|
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-May to mid-October | Statement: [Mu Ko Similan National Park, closedMonthsApprox, mid-May to mid-October]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedMonthsApprox Context triple: [Mu Ko Similan National Park, closedMonthsApprox, mid-May to mid-October]
-
A.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
B.
closureYear
Indicates the year in which an entity (such as an organization, facility, or service) ceased operations or was officially closed.
-
C.
closedDuring
chosen
Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
-
D.
closedBefore
Indicates that one entity was closed at an earlier time than another entity.
-
E.
closedBy
Indicates that one entity performs the action of closing, finishing, or terminating another entity (such as a task, issue, or process).
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdac7b34819086293d161245c529 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:14 p.m.