Triple
T13868028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Policarpo |
E333378
|
entity |
| Predicate | timezone |
P109
|
FINISHED |
| Object | Philippine Standard Time |
E90012
|
NE 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: Philippine Standard Time | Statement: [San Policarpo, timezone, Philippine Standard Time]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Philippine Standard Time Context triple: [San Policarpo, timezone, Philippine Standard Time]
-
A.
Philippine Standard Time
chosen
Philippine Standard Time is the official time zone of the Philippines, observed as UTC+8 without daylight saving time.
-
B.
Brunei Darussalam Time
Brunei Darussalam Time is the standard time zone used throughout Brunei, set at UTC+8 with no daylight saving time.
-
C.
Indochina Time
Indochina Time is the standard time zone (UTC+7) used in several Southeast Asian countries, including Thailand, Vietnam, Cambodia, and Laos.
-
D.
Chamorro Standard Time
Chamorro Standard Time is the time zone used in Guam and the Northern Mariana Islands, corresponding to UTC+10:00.
-
E.
Myanmar Standard Time
Myanmar Standard Time is the time zone used throughout Myanmar, set at UTC+6:30 with no daylight saving time.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de05c530148190b11704300bbd5f9b |
completed | April 14, 2026, 9:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c1039128819086cfe9f966b9f142 |
completed | May 3, 2026, 9:41 p.m. |
Created at: April 9, 2026, 10:14 p.m.