Triple
T15833326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | صندوق الاستثمارات العامة |
E383923
|
entity |
| Predicate | المنطقة_الزمنية |
P103460
|
FINISHED |
| Object | توقيت السعودية (UTC+3) |
—
|
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: توقيت السعودية (UTC+3) | Statement: [صندوق الاستثمارات العامة, المنطقة_الزمنية, توقيت السعودية (UTC+3)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: المنطقة_الزمنية Context triple: [صندوق الاستثمارات العامة, المنطقة_الزمنية, توقيت السعودية (UTC+3)]
-
A.
timeZoneArea
chosen
Indicates the geographic area or region for which a particular time zone is defined or applicable.
-
B.
timeZoneRegionOf
Indicates that a time zone is the official or primary time zone used within a specified geographic region.
-
C.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
D.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
-
E.
timeInRegion
Indicates that a specified amount of time is spent, occurs, or is measured within a particular geographic or defined region.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e6670d48190a456581dd951f168 |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.