Triple
T15957859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia/Hebron |
E386980
|
entity |
| Predicate | ianaTzdbName |
P6294
|
FINISHED |
| Object | Asia/Hebron |
—
|
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: Asia/Hebron | Statement: [Asia/Hebron, ianaTzdbName, Asia/Hebron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ianaTzdbName Context triple: [Asia/Hebron, ianaTzdbName, Asia/Hebron]
-
A.
ianaTimeZoneNameFormat
Indicates how a time-related value is represented or labeled according to the IANA time zone naming convention.
-
B.
ianaTimeZoneId
chosen
Indicates the association between an entity and its time zone as identified by a standard IANA time zone identifier (e.g., "America/New_York").
-
C.
timeZoneDatabase
Indicates that there is an association between something (such as a system, service, or region) and a specific time zone database it uses or is defined by.
-
D.
timeZoneName
Indicates the specific time zone designation (such as its standard name or label) associated with an entity.
-
E.
IANATimeZoneIdentifierExample
Indicates that the relationship provides an example of an IANA time zone identifier corresponding to a given time zone or context.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.