Triple
T14521754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | شلن صومالي |
E340667
|
entity |
| Predicate | المنطقة_الزمنية_للاستخدام |
P103460
|
FINISHED |
| Object | منذ_1962_وما_بعدها |
—
|
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: منذ_1962_وما_بعدها | Statement: [شلن صومالي, المنطقة_الزمنية_للاستخدام, منذ_1962_وما_بعدها]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: المنطقة_الزمنية_للاستخدام Context triple: [شلن صومالي, المنطقة_الزمنية_للاستخدام, منذ_1962_وما_بعدها]
-
A.
usedRegion
Indicates that an entity operates in, applies to, or is utilized within a specified geographic or administrative region.
-
B.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
C.
timeZoneArea
chosen
Indicates the geographic area or region for which a particular time zone is defined or applicable.
-
D.
zoneType
Indicates the classification or category of a zone that specifies its type or functional designation.
-
E.
zoneBased
Indicates that the relationship or action is determined or constrained by specific geographic or logical zones.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a72cff08190878b4bed9b0b5eb5 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.