Triple
T15957848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia/Hebron |
E386980
|
entity |
| Predicate | olsonFormatName |
P12953
|
FINISHED |
| Object | Asia/Hebron |
E386980
|
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: Asia/Hebron | Statement: [Asia/Hebron, olsonFormatName, Asia/Hebron]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asia/Hebron Context triple: [Asia/Hebron, olsonFormatName, Asia/Hebron]
-
A.
Asia/Hebron
chosen
Asia/Hebron is an IANA time zone identifier covering the Hebron area in the Palestinian territories, typically aligned with Eastern European Time and its daylight saving adjustments.
-
B.
Asia/Jerusalem
Asia/Jerusalem is the IANA time zone identifier covering the local civil time used in Jerusalem and throughout Israel.
-
C.
Asia/Aden
Asia/Aden is an IANA time zone identifier representing the standard time observed in Aden, Yemen, within the Asia region.
-
D.
Asia/Damascus
Asia/Damascus is the IANA time zone identifier representing the local civil time observed in Damascus, Syria.
-
E.
Asia/Baghdad
Asia/Baghdad is the IANA time zone identifier representing the local time for Baghdad, Iraq.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156fd7ce08190b5db4b486ccb6e40 |
completed | April 16, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffcf16b1b881909768d18b889260da |
completed | May 10, 2026, 12:19 a.m. |
Created at: April 10, 2026, 4:53 a.m.