Triple
T23756258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mu Ko Similan National Park |
E587123
|
entity |
| Predicate | openMonthsApprox |
P100126
|
FINISHED |
| Object | mid-October to mid-May |
—
|
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-October to mid-May | Statement: [Mu Ko Similan National Park, openMonthsApprox, mid-October to mid-May]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openMonthsApprox Context triple: [Mu Ko Similan National Park, openMonthsApprox, mid-October to mid-May]
-
A.
operatingMonthsApproximate
chosen
Indicates that the time period during which something operates is specified in approximate months rather than exact dates.
-
B.
openingDateApproximate
Indicates that the date when something was opened or began is not known exactly and is only an approximate value.
-
C.
typicallyOpenFromMonth
Indicates the month from which something (such as a place, service, or facility) is usually open or begins operating.
-
D.
typicalContractMonths
Indicates the usual or standard number of months that a contract is expected to run.
-
E.
hasMonthCount
Indicates a relationship where an entity is associated with a specific number of months.
- 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.